Reference
Compatibility checks
What Cronkick checks before it turns a workflow on, and how to fix each one.
A workflow that fails any of these checks is marked Needs a fix on your dashboard and isn’t triggered until you push a fix. The dashboard names the exact problem.
Checks and fixes
| No workflow_dispatch | Add workflow_dispatch: under on:. Cronkick can only start workflows through it. |
|---|---|
| Required input | Give every workflow_dispatch input a default, or make it optional. Cronkick sends no inputs. |
| schedule: still there | Remove the schedule: block, or GitHub runs the workflow a second time. See Moving from schedule:. |
| Reads the schedule event | The workflow uses github.event.schedule or checks github.event_name == 'schedule'. Both are different in a dispatched run; check for workflow_dispatch instead. |
| Too fast for the plan | The cron runs more often than your plan allows. Slow it down, or see Plans and limits. |
| Can’t be read | The marker or the cron has a typo. Compare it with the marker syntax. |