GovOPlaN/govoplan-ops
2
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Document workflow recovery operations

Browse Source
This commit is contained in:
zemion
2026-08-03 06:37:45 +02:00
parent e5f4021de9
commit 0b4e601719
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5
View File
@@ -61,3 +61,8 @@ never retry the original effect merely because its caller state is incomplete.
For Dataflow, a database-only run is atomic. A published-output run is forward For Dataflow, a database-only run is atomic. A published-output run is forward
recovery: inspect its recorded output digest and sink idempotency key, and do recovery: inspect its recorded output digest and sink idempotency key, and do
not start another publication while its state is `outcome_unknown`. not start another publication while its state is `outcome_unknown`.
For Workflow Engine, Ops exposes the action operation and evidence chain while
the Workflow handoff remains the reconciliation surface. Verify the provider,
then record **Effect confirmed** to continue without replay or **Effect absent**
to enable a deliberate retry. Instance, trigger-delivery, and timer leases show
which runtime currently owns transition authority across hosts.