What HTTP status code means my cron job succeeded?

Any 2xx status code (200 OK, 201 Created, 202 Accepted, 204 No Content) indicates success. CronJobPro marks your cron job execution as completed when it receives a 2xx response. The most common success code is 200 OK, which means the server processed the request and returned a response body.

Does CronJobPro retry when it gets a 500 error?

Yes. When CronJobPro receives a 5xx server error (500, 502, 503, 504, etc.), it automatically retries the request using exponential backoff. Server errors are typically transient, so retrying after a delay often succeeds. You can configure the maximum number of retries and the backoff interval in your job settings.

How does CronJobPro handle 301 and 302 redirects?

CronJobPro follows HTTP redirects (301, 302, 307, 308) automatically by default. It follows up to 5 redirect hops to reach the final destination. If your endpoint has moved permanently (301), consider updating the URL in your job configuration to avoid the extra redirect latency on every execution.

What happens when a cron job returns 429 Too Many Requests?

A 429 status code means the server is rate-limiting your requests. CronJobPro handles this specially by respecting the Retry-After header if present, then backing off before retrying. If your job consistently gets 429 responses, consider reducing the execution frequency or contacting the API provider to increase your rate limit.

HTTP Status Code Reference

Look up any HTTP status code to understand what it means, why it happens, and how CronJobPro handles it during cron job execution.

Search Status Codes

Monitor your cron job HTTP responses

CronJobPro logs every HTTP status code, follows redirects, retries failures with exponential backoff, and alerts you when something goes wrong.

Start Free

HTTP Status Codes and Cron Jobs

When CronJobPro executes your cron job, it sends an HTTP request to your endpoint and receives an HTTP status code in the response. This three-digit number tells CronJobPro exactly what happened: whether the job succeeded, the endpoint moved, access was denied, or the server encountered an error. Understanding these codes is essential for diagnosing why a cron job succeeded, failed, or was retried.

CronJobPro handles each category of status code differently. Success codes (2xx) mark the execution as completed. Redirects (3xx) are followed automatically so your job reaches the final destination. Client errors (4xx) are not retried because they indicate a problem with the request configuration that repeating the same request will not fix. Server errors (5xx) are retried with exponential backoff because they are usually transient.

Every execution in your CronJobPro dashboard shows the HTTP status code, response time, response headers, and body. This gives you full visibility into what your endpoint returned, making it easy to debug issues. You can also set up alerts to notify you when a job returns an unexpected status code, so you can react before it impacts your users.

Status Code Categories

1xxInformational

Informational status codes (100-199) indicate that the server received the request and is continuing to process it. These are interim responses that you will rarely see in practice. CronJobPro handles them transparently as part of the HTTP protocol negotiation.

2xxSuccess

Success codes (200-299) mean your cron job executed correctly. The most common is 200 OK, but you might also see 201 Created when your job creates a resource, 202 Accepted for asynchronous processing, or 204 No Content for endpoints that perform an action without returning data. All 2xx codes are treated as successful executions by CronJobPro.

3xxRedirection

Redirect codes (300-399) tell CronJobPro that the resource has moved. CronJobPro follows redirects automatically, supporting up to 5 hops. If you see 301 Moved Permanently in your logs, update your job URL to the new location to save the extra round-trip on every execution. Temporary redirects (302, 307) should be left as-is since the original URL may become valid again.

4xxClient Error

Client error codes (400-499) indicate a problem with the request itself. Common culprits include wrong URLs (404), missing authentication (401), insufficient permissions (403), and rate limiting (429). CronJobPro does not retry most 4xx errors because sending the same broken request again will produce the same error. The exception is 408 Request Timeout and 429 Too Many Requests, which are retried with backoff.

5xxServer Error

Server error codes (500-599) mean something went wrong on the server side. These are typically transient: a momentary overload, a deployment in progress, or a database hiccup. CronJobPro retries all 5xx errors using exponential backoff, waiting progressively longer between each attempt. If all retries fail, CronJobPro sends you an alert so you can investigate. For Cloudflare-specific errors (520-524), check both your origin server and Cloudflare configuration.

Related Resources

HTTP Status Code

Learn the full definition and history of HTTP status codes.

Retry Logic

How CronJobPro retries failed requests with exponential backoff.

HTTP Methods Guide

Understand GET, POST, PUT, DELETE and when to use each one.

Why Is My Cron Job Not Running?

Troubleshoot common issues including HTTP errors and timeouts.