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
now that we have two TW's (primary and canary) we should avoid that a TW restarts overwrites the TW assignment of QUEUED tasks and any other "interference"
at the moment both primary and canary pick tasks QUEUED by either, set to NEW and then primary handles them again as new with a new decision if to assign to canary or not.
This makes for non-reproducible behavior and makes it difficult to debug.
Once the initial decision on which TW handles a task is taken, it should stay there.
The text was updated successfully, but these errors were encountered:
now that we have two TW's (primary and canary) we should avoid that a TW restarts overwrites the TW assignment of QUEUED tasks and any other "interference"
at the moment both primary and canary pick tasks QUEUED by either, set to NEW and then primary handles them again as new with a new decision if to assign to canary or not.
This makes for non-reproducible behavior and makes it difficult to debug.
Once the initial decision on which TW handles a task is taken, it should stay there.
The text was updated successfully, but these errors were encountered: