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
we are experiencing a behaviour in our decider (and activity) worker where a new pollForDecisionTask connection is created (identified from aws client logging) every time a new workflow instance is created.
When the worker is first deployed we see log like the following every 60 seconds (default long polling period)
after we start a new workflow execution, and the decider go through its logic and activities then we start seeing another log for pollForDecisionTask.
Is that the expected behaviour ? or is there some kind of clean up we need to do when the execution is suppose to be terminated ?
we have been fighting this issue for a while now, as the time goes the response time for task.response.respondCompleted become very very slow (5 mins +).
The text was updated successfully, but these errors were encountered:
we are experiencing a behaviour in our decider (and activity) worker where a new
pollForDecisionTask
connection is created (identified from aws client logging) every time a new workflow instance is created.When the worker is first deployed we see log like the following every 60 seconds (default long polling period)
after we start a new workflow execution, and the decider go through its logic and activities then we start seeing another log for
pollForDecisionTask
.Is that the expected behaviour ? or is there some kind of clean up we need to do when the execution is suppose to be terminated ?
we have been fighting this issue for a while now, as the time goes the response time for
task.response.respondCompleted
become very very slow (5 mins +).The text was updated successfully, but these errors were encountered: