What is Execution Status?
The outcome classification of a job run: success, failure, timeout, or skipped.
Definition
Execution status categorizes the result of a job execution. Common statuses include: Success (the job completed and returned an acceptable response), Failure (the job encountered an error or returned an error status code), Timeout (the job did not complete within the allowed time), and Skipped (the execution was intentionally not run due to concurrency policies or maintenance windows).
Simple Analogy
Like a delivery status on a package: "Delivered" (success), "Failed Delivery" (failure), "Timed Out at Depot" (timeout), or "Held for Later" (skipped).
Why It Matters
Execution status is the primary indicator of your automation's health. A string of successful statuses means things are working. A failure status triggers investigation and possibly retries. CronJobPro uses status to drive alerting, retry logic, and dashboard health indicators.
How to Verify
CronJobPro shows status with color-coded indicators: green for success, red for failure, yellow for timeout. Dashboard summaries show success rates over time. Set up alerts to be notified immediately when a status changes to failure.
Common Mistakes
Treating all non-success statuses the same — a timeout requires different remediation than a 404 error. Not configuring what counts as "success" — some APIs return 200 even when there is an error in the response body. Ignoring "skipped" statuses that might indicate a systematic problem.
Best Practices
Define clear success criteria beyond just the HTTP status code. Use CronJobPro's response validation to check for expected content in the response body. Set up separate alerts for different failure types so you can prioritize response.
Documentation
Read the full docs
Try it free →Frequently Asked Questions
What is Execution Status?
Execution status categorizes the result of a job execution. Common statuses include: Success (the job completed and returned an acceptable response), Failure (the job encountered an error or returned an error status code), Timeout (the job did not complete within the allowed time), and Skipped (the execution was intentionally not run due to concurrency policies or maintenance windows).
Why does Execution Status matter for cron jobs?
Execution status is the primary indicator of your automation's health. A string of successful statuses means things are working. A failure status triggers investigation and possibly retries. CronJobPro uses status to drive alerting, retry logic, and dashboard health indicators.
What are best practices for Execution Status?
Define clear success criteria beyond just the HTTP status code. Use CronJobPro's response validation to check for expected content in the response body. Set up separate alerts for different failure types so you can prioritize response.
Related Terms
Execution
A single instance of a job running, from start to completion or failure.
Exit Code
A numeric value returned by a process to indicate success (0) or a specific type of failure.
HTTP Status Code
A three-digit number returned by a server indicating the result of an HTTP request.
Alerting
Automated notifications sent when a job fails, times out, or behaves abnormally.