Deriving Workflow Status from Real Transition Evidence
Repair a workflow report that advances too early by filtering invalid events, normalizing legacy stages, recovering from business evidence, and recording milestones only when transitions occur.
TAGTags
idempotency
7 articles
Designing Rerunnable Oracle Schema Synchronization with Wrong-Target Guards
Turn an Oracle change list into a fail-closed synchronization program with target identity checks, full preflight validation, conditional DDL, business-key MERGE, and repeat-run proof.
Preventing Duplicate Delivery Across Automation Threads
How a destination-and-content idempotency key, unknown-result handling, and repeated sibling-task checks can stop resumed automation from repeating an external side effect.
Safely Revising Completed Jobs with a Fail-Closed State Machine
How an explicit revision lifecycle can reopen a completed external-delivery job without duplicating remote objects or trusting stale review evidence.
Pin Policy Snapshots Before Long-Running Automation Executes
How versioned policy snapshots keep active jobs and retries reproducible while new rules roll out prospectively.
Assigning Incrementing Job IDs Without Duplicating Paid Work on Retry
How a stable allocation key and a process lock let a recurring paid pipeline create several jobs per period without duplicating work when a scheduled run retries.
Building a Production-Grade WMS RF Application
A WMS RF migration centered on warehouse-scoped identity, shared domain rules, idempotent writes, offline recovery, and native printing.