← Back to list
01Issue
BugShippedSwamp ClubPublic
AssigneesNone
Relationships
↔ sibling #4556#4491 Manual: the REST API page still says cancelling a workflow run needs admin
Opened by skunk-ape · 11/7/2026· Shipped 11/10/2026
Problem
Since #4485, content/manual/reference/swamp-serve/rest-api.md is wrong about who can cancel a workflow run:
- The intro says every endpoint on the page except health and
GET /needs admin. POST /api/v1/cancel/:type/:idlists403"cancel requires admin permission" for any non-admin token.
What's true now
workflow-runneedsrunon the run's workflow, for any run of it, or admin onaccess:*.- A refused caller gets the same
404as a missing run, a finished run or another workflow's run, so that route no longer answers403for lack of permission on a run. method-runand bulkPOST /api/v1/cancelstill need admin.--restricted-commands workflow.cancelkeeps cancelling admin-only, on both the HTTP route and theworkflow.cancelrequest the dashboard uses.- Cancelling a parent also cancels the suspended children it waited on, including on workflows where the caller holds no grant.
The rule is in design/enablers/access-control.md under "Who can cancel a run" in the swamp repo.
Scope
Docs only, in swamp-club. Correct rest-api.md, add workflow.cancel to the restricted commands section of reference/swamp-serve/authorization.md, and check that reference/workflows#execution-cancellation agrees.
Done when
- The REST API page's status table and intro match the rules above for each
:type. - The restricted commands section names
workflow.cancel.
02Bog Flow
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse
Editable. Press Enter to edit.
system commented 11/7/2026, 1:20:42 AM
Classified automatically when this issue was filed.
- Source: Swamp Club
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.