You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mahammad@Geant reports that the process detail page doens't update throught the websocket connection when there are callback steps in his form. The websocket connection is established and the backend sends the correct cache invalidation requests, it appears to stop doing that when a callback step is reached.
When using the ThreadPool executor, the callback_step does not send a websocket message to the frontend for the validation step. The frontend does not update and you don't see that it has failed until refreshing.
I have not been able to reproduce the problem inside Celery executor, so I would assume the problem has to do with ProcessDataBroadcastThread.
steps to reproduce
create a workflow with a callback_step
run the workflow and make sure that the validation step in the callback_step raises an error.
see that the frontend does not receive a websocket message to update the process detail page data.
Version
2.7.5
What python version are you seeing the problem on?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
This issue was addressed in frontend workfloworchestrator/orchestrator-ui-library#1456 and after looking into it we found out that it is a backend issue.
When using the ThreadPool executor, the callback_step does not send a websocket message to the frontend for the validation step. The frontend does not update and you don't see that it has failed until refreshing.
I have not been able to reproduce the problem inside Celery executor, so I would assume the problem has to do with
ProcessDataBroadcastThread
.steps to reproduce
Version
2.7.5
What python version are you seeing the problem on?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: