-
Notifications
You must be signed in to change notification settings - Fork 895
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: flows sometimes does not terminate #4708
Comments
Hi @LK511, Thank you for reporting the issue. Are you using Docker Compose (with Redis/Postgres) or just a plain Docker image? Do you see any errors in the backend logs? I think the flow threw an unexpected error that wasn't handled by the engine and stopped. |
In the docker container log, I see following: The application started on https://apTest.backlogcom.onmicrosoft.com/, as specified by the AP_FRONTEND_URL variables. It looks like it still starts the same flow. if I understand the log properly, but there is started only one flow in the run tab: I see no Error in the log. I am using Docker image connected to our Postgres and Redis DB. The used user has all permissions enabled, no limitations on the user are set. I am using the user for managing everything in the database. |
I have found a solution, how to solve this issue. There was AP_QUEUE_MODE set to REDIS, which caused the freeze. When I changed it to MEMORY, it is running correctly. But with memory, the response latency of the AP web UI is incerased many times. |
Bug decription
There is sometimes happening, flow freeze. It runs properly when I test it step by step. Flow sometimes freezes, when I start it from webhook or by test flow button on the same data. (It happened on many flows, not only one.)
To Reproduce freeze what I did in my instance
Steps to reproduce the behavior:
Expected behavior
Flow will always finish in a fail or in finished status, not stay in the running forever. I have flows, which shows running status many days
Screenshots
Running flow which does not terminate:
2 days running flow which does nothing:
Additional context
This usually happens, when it is started via webhook. When I open running flow, there is no information on which piece it is blocked, all pieces have a running circle icon.
There is no button to stop too long running flows started via webhook? There is set 600 to max timeout in the .env docker, but it seems, it does nothing when I change the value.
The text was updated successfully, but these errors were encountered: