Alireza04/07/2023, 6:25 AM
Marvin04/07/2023, 6:25 AM
Nate04/07/2023, 3:25 PM
, which suggests that the process running your flow received a
signal, which terminates it immediately. This can happen due to various reasons, such as: 1. Reaching a resource limit (e.g., memory or CPU usage) on your system or container, causing the operating system or orchestrator to forcefully kill the process. 2. A user or admin intentionally killing the process. 3. An unrecoverable error, panic, or crash in the underlying runtime or system libraries causing the process termination. To narrow down the issue and find a solution, consider the following steps: 1. Inspect logs from the flow run, agent, or any related infrastructure to identify the cause of the termination. Look for possible memory, CPU, or other resource usage issues, as well as any error messages or stack traces. 2. Check your system or container limits and adjust them if necessary to ensure the process has sufficient resources to execute. 3. Investigate the dependencies, environment, or configurations of your flow that might contribute to the issue. Identifying the root cause using the context provided by logs and your specific system will help you determine the best course of action to resolve the issue. If you have more information or questions, feel free to share, and I'll help you further.