You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ux(planned-purchases): Pause should be visible + reversible, not a silent removal (QA 6.1 follow-up) #903
PR #779/#772 fixed the SQL crash by adding paused to the valid_status CHECK constraint on purchase_executions. But now clicking Pause on a scheduled (planned) purchase makes the row silently DISAPPEAR from the list with no feedback and no visible change to the plan. A Pause that looks like a delete is an anti-pattern.
Root cause (suspected)
The planned-purchases list query filters to active statuses (e.g. pending/scheduled) and excludes paused, so paused executions drop out of the rendered list. There is no success toast and no way to un-pause.
Desired behavior
Keep the row VISIBLE with a clear Paused status badge (do not drop it).
Success toast on pause ("Purchase paused").
Add a Resume action to un-pause (paused -> pending/scheduled).
Paused executions are excluded from firing but stay listed (or under a Paused filter).
QA Planned 6.1 follow-up
Current behavior (bug)
PR #779/#772 fixed the SQL crash by adding
pausedto thevalid_statusCHECK constraint onpurchase_executions. But now clicking Pause on a scheduled (planned) purchase makes the row silently DISAPPEAR from the list with no feedback and no visible change to the plan. A Pause that looks like a delete is an anti-pattern.Root cause (suspected)
The planned-purchases list query filters to active statuses (e.g.
pending/scheduled) and excludespaused, so paused executions drop out of the rendered list. There is no success toast and no way to un-pause.Desired behavior
paused->pending/scheduled).Notes
pausedDB status and theTransitionExecutionStatusmachinery exists from Pause scheduled purchase fails with valid_status CHECK constraint violation (Planned 6.1) #772.Labels: triaged priority/p2 severity/medium urgency/this-sprint impact/many effort/m type/bug