Konsistente Ablaufdaten

Data & Workflow Consistency

A workflow can show a green "Success!" toast in the UI while leaving orphaned rows, stale counters, out-of-sync caches, or stuck background jobs underneath. Always verify state consistency end to end.

Workflow

1. Check multi-surface state agreement:
   • After performing a create, update, state transition, cancellation, or deletion, verify that the new state agrees across:
     • The immediate response view.
     • The parent list / board / summary counter after a full page reload.
     • Audit logs / event streams / activity timelines.
     • Downstream exports, search indexes, and detail pages.
2. Verify lifecycle transitions and terminal states:
   • Trace the entity's state machine (draft -> ready -> running -> waiting_approval -> completed / failed / cancelled):
     • Confirm invalid transitions (e.g., cancelling an already completed item, or approving a cancelled run) are rejected cleanly.
     • When a running workflow is interrupted or cancelled, verify that active child tasks/workers stop and the parent record transitions to a consistent recoverable state.
3. Inspect failure atomicity (No Half-Done State):
   • When step 2 of a 3-step operation fails:
     • Either the entire transaction rolls back cleanly, or the workflow records an explicit partial/compensating state that the user can safely retry or resolve.
     • Verify that retrying a failed operation does not create duplicate child items, double charges, or duplicate notifications.
4. Verify deletion, archival, and retention cleanup:
   • Check what happens to child records, active runs, attachments, and references when a parent project, task, or user is deleted or archived.