Why: when a trigger's field mapping doesn't match an incoming event, dispatch skips the trigger and logs it. Nothing is recorded on the event or the trigger's dispatch history, so the operator can't see why a workflow didn't start.
Done when: a skipped dispatch is recorded with its reason on the event and in the trigger's dispatch history, and shown on the captures page.
**Why**: when a trigger's field mapping doesn't match an incoming event, dispatch skips the trigger and logs it. Nothing is recorded on the event or the trigger's dispatch history, so the operator can't see why a workflow didn't start.
**Done when**: a skipped dispatch is recorded with its reason on the event and in the trigger's dispatch history, and shown on the captures page.
sam
added the bugmedium labels 2026-11-22 00:48:35 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: when a trigger's field mapping doesn't match an incoming event, dispatch skips the trigger and logs it. Nothing is recorded on the event or the trigger's dispatch history, so the operator can't see why a workflow didn't start.
Done when: a skipped dispatch is recorded with its reason on the event and in the trigger's dispatch history, and shown on the captures page.