Troubleshoot CRD API Integrations
Check authentication, request shape, identifiers, and service health.
401 Unauthorized
Check that you requested a token from the configured CRD token operation and sent it as Authorization: Bearer
400 or 500 responses
For operations that document these responses, check required path and query values and validate JSON against the operation schema. A 500 response is documented as an operation exception; details vary by operation. Do not infer a specific cause from status alone.
Wrong or missing schedule
Resolve the schedule using folder lookup operations. Keep ScheduleType and UniqueId paired and use exact values returned by CRD.
Execution appears stuck
Check IsSchedulerRunning, the execution queue, and execution status. Use cancel or terminate only after confirming the target identifier; these operations affect running work.
For operation parameters and response codes, see the API Reference.
Updated about 5 hours ago