Reference

Statuses

What each status on your dashboard means.

Each run

Each planned run on your dashboard has one of these statuses. It describes Cronkick’s part: getting the run started.

Due	Waiting for its scheduled time.
Sending	Due now; Cronkick is sending it.
Overdue	Over a minute past its scheduled time and Cronkick hasn’t sent it yet.
Started	GitHub created the run.
Sent	GitHub accepted the request; the run is not linked yet.
Unconfirmed	Cronkick sent it but could not confirm GitHub got it, so it did not resend.
Refused	GitHub refused the trigger, so Cronkick did not retry. The note says why.
Gave up	Not sent before its deadline, so Cronkick skipped it rather than run it late. The note says why.
Skipped	Not sent: the schedule was paused or changed.

A run counts as on time when GitHub accepted the request within 30 seconds of its scheduled time. See Timing and retries.

Cronkick outages

Cronkick plans runs up to 2 hours ahead. A planned run that Cronkick didn’t send before its deadline shows as Gave up with the note “Cronkick didn’t send it before its deadline”.

If Cronkick’s scheduler stops for more than 2 hours, the dashboard shows one outage window, from its last planning pass to when planning resumed, rather than inventing a row per missed time. Runs due then may not have been sent; any that were sent are listed in the history. See When Cronkick is down.

The run’s result

The GitHub run’s own result (passed, failed, cancelled) is shown next to the status, exactly as GitHub reports it. A run can be started on time by Cronkick and still fail on GitHub.

Each workflow

Active	Cronkick triggers it on schedule.
Needs a fix	Something would break a dispatched run. See Compatibility checks.
Paused	Over your plan’s schedule limit. See which schedules pause.