Hi Temporal community,
I’m working on FCI (Formal Conservative Interposition), a research project about safe recovery before external actions. I would appreciate help identifying the strongest standard Temporal-based design to use as a comparison.
I have read the discussions on external-call idempotency, authorization/execution drift, and the recent Truth Engine experiment. I understand that an intermediary cannot guarantee exactly-once effects against a non-idempotent target that offers no reliable reconciliation.
My question concerns recovery across a Workflow Reset, rather than ordinary Activity retries.
Consider a logical business operation K:
- An Activity requests an external effect.
- The target may commit it, but the response is lost before Activity completion is recorded.
- An operator resets the Workflow to a point before that Activity.
- The new execution reaches the operation again.
For this scenario, Temporal’s persistence is not restored from a backup, and the target’s state remains intact. The reset is not assumed to erase the original execution’s history or undo external effects.
We want to test two outcomes:
- If K already committed, recovery produces no second effect.
- If K never committed, recovery can eventually complete it once the required services are available and authorization remains valid.
Would a business-operation ID preserved across runs, combined with target-side atomic deduplication and result lookup, be the recommended baseline?
In particular:
- How would you preserve K across Reset while distinguishing a retry from a genuinely new business operation?
- What atomicity and retention guarantees must the target provide?
- Is there an existing sample or failure-injection test covering this sequence, including an earlier Activity attempt that may still be running?
If the target lacks those guarantees, identifying precisely when recovery must remain blocked or require reconciliation would also be valuable.
The goal is a reproducible comparison, including the possibility that standard mechanisms already provide everything this scenario requires.
Thank you for any corrections or references.
Alexandre Couret