Temporal Workflow Versioning Language Collocations
Practise the standard verbs for versioning Temporal workflows safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a version marker inside a workflow before changing its logic, so an already-running execution keeps following its original code path deterministically.'
We 'add a marker' — the standard, simple collocation for inserting a versioning check into workflow code. The other options are less idiomatic here.
2 / 5
Fill in: 'Changing a workflow's logic without any version guard can ___ an already-running execution failing a replay check the moment history no longer matches the new code.'
We say an unguarded change will 'leave' running executions failing replay — the standard, natural collocation for the resulting non-determinism error. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every workflow change against replay tests built from real production histories, so a subtle non-determinism bug is caught before it reaches a live worker.'
We 'test' a change — the standard, simple collocation for validating workflow code before deploying new workers. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ old workflow code paths only once every in-flight execution that depends on them has completed, rather than removing them the moment the new logic ships.'
We 'remove code paths' — the standard, simple collocation for deleting logic that's genuinely no longer needed. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ active workflow versions across the fleet periodically, so a worker still running month-old logic isn't discovered only when it produces an unexpected result.'
We 'audit' versions — the standard, simple collocation for periodically reviewing which code is actually deployed. The other options are less idiomatic here.