Monitor CRD API Schedule Executions

When an asynchronous CRD API request returns an ExecutionId, save it and use the execution-status operation to follow that run.

Track the execution

1. Submit the schedule once and store its ExecutionId.
2. Check status for that ID at regular intervals appropriate to your integration.
3. Stop checking when the API reports a final state or your integration’s waiting period ends.
4. Review the final result and any error details.
5. Check the destination to confirm that the report was delivered.

If your waiting period ends before a final status is available, check the existing execution and destination before submitting another run. A delayed status response does not mean the schedule failed.

Use CRD history and error views

The CRD System Monitor provides History View and Error Log for additional investigation. It does not have a dedicated API execution queue. Use the API’s execution-status operation to track an API run, and the relevant history or error view for more context.

Related CRD API resources

• Monitor, Recover, and Reconcile Executions
• Quick Start: Execute and Monitor a Schedule
• API Reference
• Use the CRD System Monitor
• Execute a CRD Schedule Through the REST API