Skip to main content
A run is a record of a single webhook execution. Every time a cron fires on schedule, a job reaches its scheduled time, or you manually trigger either one, CronAPI logs a run with the result.

​
Run object

FieldTypeDescription
idstringUnique identifier (UUID)
cron_idstring | nullAssociated cron ID (null for job runs)
job_idstring | nullAssociated job ID (null for cron runs)
request_idstring | nullRequest identifier
status_codeintegerHTTP status code returned by the webhook
successbooleantrue if the status code is 2xx
response_time_msintegerTime taken in milliseconds
errorstring | nullError message or response body on failure
fired_atstringISO 8601 timestamp of when the webhook was fired

​
Viewing runs

Retrieve the last 50 runs for a specific cron or job: 
curl https://app.cronapi.dev/api/v1/crons/:id/runs \
  -H "Authorization: Bearer your_api_key_here"
Runs are returned in reverse chronological order (most recent first).

​
Success and failure

Outcomesuccesserror
2xx responsetruenull
4xx/5xx responsefalseResponse body
Request timeoutfalse"Request timed out"
Network errorfalseException message

​
Timeout

All webhook requests have a 30-second timeout. If your endpoint does not respond within 30 seconds, the run is recorded as failed with the error "Request timed out".

​
Automatic cleanup

Runs associated with a cron are automatically deleted when the cron is deleted.