← Back to Bug fix
See how it helps
Workflow data consistency
Checks that lifecycle changes agree across lists, details, events and persistent state, including partial failures.
data-workflow-consistency
Workflow agents using this skill
When is it useful?
Use when a completed operation still appears pending elsewhere.
What does it help you do?
- Compares related views and stored state after each transition.
- Checks terminal states cannot accidentally reopen or repeat side effects.
- Inspects interrupted writes and archival or deletion effects within authorized scope.
Try asking this
Trace cancellation across detail, dashboard and background job state; identify any contradictory or half-completed result. Cancel while a worker is finishing. The detail page, counters and audit history should agree, with no completed external action silently erased.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
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
- 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.
- After performing a create, update, state transition, cancellation, or deletion, verify that the new state agrees across:
- 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.
- Trace the entity's state machine (
- 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.
- When step 2 of a 3-step operation fails:
- 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.
Included files 1
SKILL.md