Skip to main content
Find recent errors for a project, then use request, trace, or run IDs to follow the affected execution. Replace support-assistant with the project that owns the work. Use an API credential with access to its observability data.

​
1. Find error logs

Search error logs with GET /projects/{project_reference}/logs:
query-logs.sh
Use the returned next_cursor to continue through log results. Keep the same filters when paging. List traces with GET /projects/{project_reference}/traces:
query-traces.sh
Add start and end to limit the time window. If you have a run ID, add run_id to the trace query instead of searching unrelated activity.

​
Verify the result

Match the record’s project, timestamp, and identifiers to the failing execution. A nearby error is not necessarily the cause of the request you are investigating. Logs describe individual messages. Traces connect timed operations. Run events record execution progress and output; they complement the trace.

​
Next