# context canceled ## Symptoms * fylr (execserver part of fylr) may output / log something like this message: ``` ERR exec #0: signal: killed [context canceled] Env=execserver ``` * Also, the execserver job probably does not achieve what it is supposed to (as it was aborted). May result in missing preview, missing extracted metadata etc.. ## Cause Processing of an asset file used more time than the configured timeout (or, less likely, tried to use more memory than the configured limit). ## Solutions * Increase the timeout in `fylr.yml`. Default: ```yaml fylr+: execserver+: pluginJobTimeoutSec: 2400 ``` * Reduce load on the hardware so that processing per asset is faster. All the reasons for load on your hardware are out of the scope of this fylr documentation, but to e.g. reduce the number of parallel video processing to 1 see the code block below. * Default is waitgroup `slow` instead of waitgroup `video`. Waitgroup `slow` defaults to `2` processes. ```yaml fylr+: services+: execserver+: waitgroups+: video: processes: 1 services+: ffmpeg: waitgroup: video ``` * Change the used "recipe"(=list of steps on how to process certain asset file types). About recipes see e.g. and search for the word recipe. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fylr.io/for-system-administrators/symptom-and-solution/context-canceled.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.