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
Commit 3c3b5d1
Browse filesBrowse the repository at this point in the historyBrowse files
fix(triggers): v2 reports only triggers that run, restore executor PATCH, switch all or nothing
The v2 list and block target require the active version of a deployed
workflow for both tables, since webhook processing refuses a versionless or
undeployed row; the legacy row-id routes keep the editor's view. PATCH
/api/webhooks/[id] admits a workflow run's executor delegation again, and
setTriggerEnabled admits the executor service. A multi-row switch rolls back
entirely when any row was retired or switched concurrently, so a conflict
commits nothing. Adds the two new CLI fences to the docs content baseline.
* Pausing or resuming one trigger of the live deployment. Not a deploy: the
357
369
* deployed graph and its provider registrations are untouched, so it is a
358
370
* write rather than an admin act, and a workspace key may perform it.
371
+
* A workflow run's executor delegation may too, as it could before this
372
+
* moved onto the use case.
359
373
*
360
374
* permission-group-exempt: `triggers.webhook` is asserted inside the use case and only for enabling a webhook-table row, because a group that withholds inbound webhooks must still let a member switch a live one off
0 commit comments