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
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
If an execution fails in a "wait" state, then it retains it's "currentlyWaiting" data, causing the "getExecutionDocuments" function to pick it up. This results in many noop attempts to process that failed document wasting time.
The code in "getExecutionDocuments" should only look to resume executions in the "waiting" status.
The text was updated successfully, but these errors were encountered:
If an execution fails in a "wait" state, then it retains it's "currentlyWaiting" data, causing the "getExecutionDocuments" function to pick it up. This results in many noop attempts to process that failed document wasting time.
The code in "getExecutionDocuments" should only look to resume executions in the "waiting" status.
The text was updated successfully, but these errors were encountered: