Create Cron Job

1. Cron Expression Format

Cron jobs use the standard Linux time format, consisting of 5 fields separated by spaces.

2. Common & Advanced Settings Explained

• Target URL: The endpoint that the Cron Engine will send the HTTP request to. Private IPs (127.0.0.1, localhost) are natively blocked for security.
• HTTP Method: GET, POST, DELETE... Determines the action verb sent to your server.
• Request Body: Only available for POST/PUT/PATCH/DELETE. Usually utilized for sending raw JSON payloads to your API.
• Custom Headers & Auth: Send specific metadata like Authorization: Bearer TOKEN or Content-Type: application/json. You can also use HTTP Basic Auth (Username/Password).
• Request Timeout: The maximum number of seconds the engine will wait for your server to respond. If it exceeds this limit, the request is aborted and marked as Failed.
• Auto-disable Failures: Automatically pauses the job if it continuously fails for a specified number of consecutive times. Set to 0 to only rely on system limitations.
• Response Logging: When checked, the engine records your endpoints return variables into a dashboard for debugging.

3. Execution Status & Errors

• A Job Execution is considered Successful if the HTTP response code is 200 - 399.
• If the error code is 400 or above (e.g., 404, 500, 503), the system will mark it as Failed.
• Network errors, DNS resolution failures, and connection timeouts will also be categorized as Failed (null).
• Server timezone is UTC. All precise schedule triggers will execute relative to UTC (+0).