What is Response Timeout?
The maximum time to wait for an HTTP response before considering the request failed.
Definition
Response timeout is the maximum duration a client will wait for a complete HTTP response after sending a request. If the server does not send the full response within this window, the client aborts the connection and marks the request as timed out. In CronJobPro, the response timeout is configurable per job and determines how long to wait for your endpoint to respond before triggering failure handling.
Simple Analogy
Like waiting for a friend who said they would be "right back" — after 15 minutes, you stop waiting and assume they are not coming.
Why It Matters
Response timeout protects CronJobPro from hanging connections. Without it, a slow or unresponsive endpoint could hold a connection open indefinitely, consuming resources and potentially blocking other jobs. Setting an appropriate timeout ensures that hung requests are detected and handled promptly.
How to Verify
Check the timeout setting on your CronJobPro job configuration. Test your endpoint's response time with curl: `curl -o /dev/null -s -w "%{time_total}" https://your-endpoint.com`. Monitor execution history for timeout-status runs. Set the timeout generously enough for normal operation but strict enough to catch hangs.
Common Mistakes
Setting the timeout shorter than the endpoint's normal processing time, causing false timeouts. Not distinguishing between connect timeout and response timeout. Setting extremely long timeouts (hours) that allow hung connections to persist.
Best Practices
Set response timeout to 2-3x the expected response time. Use a separate, shorter connect timeout (5-10 seconds) to detect unreachable servers quickly. For long-running jobs, return 202 Accepted immediately and use a callback for the final result. Monitor timeout trends.
HTTP Methods Guide
Learn about HTTP methods
Try it free →Frequently Asked Questions
What is Response Timeout?
Response timeout is the maximum duration a client will wait for a complete HTTP response after sending a request. If the server does not send the full response within this window, the client aborts the connection and marks the request as timed out. In CronJobPro, the response timeout is configurable per job and determines how long to wait for your endpoint to respond before triggering failure handling.
Why does Response Timeout matter for cron jobs?
Response timeout protects CronJobPro from hanging connections. Without it, a slow or unresponsive endpoint could hold a connection open indefinitely, consuming resources and potentially blocking other jobs. Setting an appropriate timeout ensures that hung requests are detected and handled promptly.
What are best practices for Response Timeout?
Set response timeout to 2-3x the expected response time. Use a separate, shorter connect timeout (5-10 seconds) to detect unreachable servers quickly. For long-running jobs, return 202 Accepted immediately and use a callback for the final result. Monitor timeout trends.
Related Terms
Timeout
The maximum time allowed for a job execution before it is forcefully terminated.
Execution Duration
The measured wall-clock time from when a job starts running to when it finishes.
Endpoint
A specific URL where an API or service receives and processes HTTP requests.
HTTP Status Code
A three-digit number returned by a server indicating the result of an HTTP request.