Skip to content
Recuro Docs

Viewing and Debugging Runs

This guide covers how to inspect execution history and diagnose failures for both crons and jobs.

Viewing cron executions

  1. Navigate to Crons in the sidebar
  2. Click on a cron to view its detail page
  3. The Recent Executions section shows the last 10 executions with status, response code, and duration
  4. Click View All Executions to see the full paginated history

Each execution shows:

  • Status: completed or failed
  • Response Status: HTTP status code (e.g., 200, 500)
  • Duration: Round-trip time in milliseconds
  • Started At / Completed At: Timestamps
  • Failure Reason: Categorized reason (if failed)
  • Error Message: Human-readable description
  • Request Headers: What was sent (including webhook signing headers)
  • Request Body: The payload sent
  • Response Body: What your endpoint returned
  • Response Headers: Headers returned by your endpoint

Viewing job runs

  1. Navigate to Jobs in the sidebar
  2. Click on a job to view its detail page
  3. The Run section shows the execution details

For jobs with retries, each retry attempt is a separate job record. The original job is linked to its retries, so you can trace the full retry chain:

  • attempt_number: Which attempt this is (1 = original, 2 = first retry, etc.)
  • is_retry: Whether this job is a retry of a previous attempt
  • final_status: The outcome (success, retrying, failed_with_retries, failed_no_retries, dead_lettered)

Understanding failure reasons

ReasonWhat happenedWhat to check
timeoutYour endpoint did not respond in timeIncrease timeout_seconds, optimize your endpoint, check for slow database queries or external dependencies
connection_errorCould not connect to your serverVerify the server is running, check firewall rules, ensure the port is open
dns_errorCould not resolve the hostnameVerify the domain name is correct, check DNS configuration
ssl_errorTLS handshake failedCheck your SSL certificate validity, ensure the certificate chain is complete
http_client_errorYour endpoint returned 4xxCheck authentication, request format, and endpoint URL
http_server_errorYour endpoint returned 5xxCheck your server logs for application errors
assertion_failedResponse did not meet assertionsReview your success assertions and compare against the actual response
invalid_urlThe URL is malformedVerify the URL format and protocol
limit_exceededMonthly request limit reachedCheck your usage in Usage and consider upgrading your plan
unknownUnexpected errorCheck the error message for details

Filtering jobs by status

On the Jobs page, use the filter dropdown to narrow results:

  • All: Show all jobs
  • Pending: Jobs waiting to be dispatched
  • Completed: Successfully finished jobs
  • Failed: Jobs that failed (includes retrying and dead-lettered)

You can also filter by queue and search by URL.

Filtering crons

On the Crons page, filter by:

  • All: Show all crons
  • Active: Currently firing crons
  • Inactive: Paused crons

Search by name or URL.

Filtering alerts

On the Alerts page, filter by:

  • Alert type: failure, warning, recovery, limit_warning
  • Failure reason: timeout, connection_error, dns_error, ssl_error, http_client_error, http_server_error, assertion_failed, invalid_url, limit_exceeded, unknown

Next steps