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
By default tink-worker must run all its workflows and actions within 1 hour of its startup. This is because we have a default 1h timeout parameter that gets used as a timeout for a root context.Context which ends up being passed down to worker.ProcessWorkflowActions that then gets used for everywhere.
Expected Behaviour
tink-worker is able to stay up and running effectively forever.
Current Behaviour
This effectively caps tink-worker's uptime to 1h.
Possible Solution
Pass down the timeout to tink-worker's main event loop so it can use it to create a new timeout when needed, likely when a new workflow is being processed (as I suspect was the original intent, iirc).
By default tink-worker must run all its workflows and actions within 1 hour of its startup. This is because we have a default 1h timeout parameter that gets used as a timeout for a root context.Context which ends up being passed down to worker.ProcessWorkflowActions that then gets used for everywhere.
Expected Behaviour
tink-worker is able to stay up and running effectively forever.
Current Behaviour
This effectively caps tink-worker's uptime to 1h.
Possible Solution
Pass down the timeout to tink-worker's main event loop so it can use it to create a new timeout when needed, likely when a new workflow is being processed (as I suspect was the original intent, iirc).
Steps to Reproduce (for bugs)
See slack thread: https://cloud-native.slack.com/archives/C01SRB41GMT/p1644596207711939
Context
tink-worker is unable to process a workflow to completion
The text was updated successfully, but these errors were encountered: