Viewing Cron Run History

Quant Cloud maintains comprehensive execution records for all scheduled tasks, providing detailed insights into cron job performance, success rates, and output. The run history interface enables you to track job execution patterns, diagnose failures, and verify that your automated tasks are performing as expected.

Each cron job execution runs in a temporary container that is created specifically for that task and destroyed upon completion. This isolation ensures that scheduled tasks never interfere with your production application performance.

Access the run history for any cron job by clicking the history icon (clock) in the Actions column of the “Manage Cron Jobs” interface.

Run History Interface

The run history page is dedicated to a single cron job, clearly identified in the page header (e.g., “Run History for process-cf-domains”). This focused view allows you to analyze the performance and reliability of individual scheduled tasks.

Page Controls

• Refresh Button: Manually reload the execution list to see the most recent runs
• Navigation Breadcrumbs: Easy navigation back to the main cron jobs management page

Execution History Table

The main content displays a comprehensive table of all job executions, organized chronologically with the most recent runs first.

Execution Details Each row in the history table provides essential information about individual job runs:

• Run ID: Unique identifier for each execution (e.g., 72560616-dd82-4092-a023-b142fdde3406)
• Status: Visual indicator of execution outcome with color-coded badges:
  • SUCCEEDED (green): Job completed successfully
  • FAILED (red): Job encountered an error during execution
  • RUNNING (blue): Job is currently executing
  • PENDING (gray): Job is queued for execution
• Created At: Timestamp when the execution was scheduled
• Started At: Actual execution start time
• Ended At: Completion timestamp for finished jobs
• Exit Code: Command exit status (0 for success, non-zero for errors)
• Actions: “View Details” button for accessing comprehensive execution information

Execution Status Indicators The status column provides immediate visual feedback about job performance:

• Successful executions show consistent SUCCEEDED status with exit code 0
• Failed runs are clearly marked and warrant investigation
• Running jobs indicate active task execution
• The chronological listing helps identify patterns in job success or failure rates

Detailed Execution Information

Clicking “View Details” for any execution opens a comprehensive modal window containing complete information about that specific job run.

Run Details Modal

The execution details modal provides a complete picture of the job run:

Execution Metadata

• Run ID: Unique execution identifier for tracking and reference
• Status: Final execution outcome (SUCCEEDED, FAILED, etc.)
• Command: Exact command that was executed in the container
• Target Container: Specific container where the command ran (e.g., php)
• Start Time: Precise timestamp when execution began
• End Time: Completion timestamp
• Exit Code: Command return code (0 indicates success)

Command Output The output section captures all information generated during command execution:

• Standard Output (stdout): Normal command output and results
• Standard Error (stderr): Error messages and diagnostic information
• Execution Logs: Platform-generated logs about the execution process

Output Display Features

• Scrollable Text Area: Navigate through large amounts of output easily
• Monospaced Font: Ensures proper formatting and readability
• Syntax Highlighting: Color-coded output for better analysis
• Copy Functionality: Easy copying of output for further analysis

Troubleshooting with Run History

Success Pattern Analysis Regular successful executions with exit code 0 indicate healthy job operation. Look for:

• Consistent execution timing
• Expected output patterns
• Stable resource usage

Failure Investigation When jobs fail, the run details provide crucial debugging information:

• Exit Codes: Non-zero codes indicate specific error conditions
• Error Output: stderr contains detailed error messages and stack traces
• Timing Issues: Compare start/end times to identify timeout problems
• Resource Constraints: Look for memory or CPU-related error messages

Performance Monitoring Track job performance trends over time:

• Execution Duration: Monitor how long jobs take to complete
• Success Rate: Identify reliability patterns
• Container Startup Time: Watch for any increases in execution times that might indicate infrastructure issues
• Task Efficiency: Optimize commands for faster execution in temporary containers

Tip

Regular review of cron job execution history helps maintain reliable automated processes. Pay special attention to any changes in execution patterns, failure rates, or performance characteristics that might indicate underlying issues requiring attention.

The comprehensive run history and detailed execution information provide the visibility needed to maintain robust, reliable scheduled task automation in your Quant Cloud environment.