Find the trace behind an inference request

Open the correct workspace

In Console, select the organisation and project that received the inference request, then open Engineering and Traces. A request sent under another workspace key will not appear in your current workspace.

Narrow the results

Inference tags are stored on usage traces and shown in the Engineering trace table. Filter by tag to find traffic for a workflow or experiment. Tags should describe the workflow; avoid putting sensitive customer information into a tag.

Connect a trace to evaluation data

A recorded trace can become a curated data asset. The data flow is capture, stage, then snapshot: the snapshot pins the data used by Lab. Read Data assets before curating or deleting data.

If you cannot find the request

• Confirm the API key's workspace and the application's project attribution.
• Check the date range and tag filters rather than assuming an empty list means a database failure.
• Record the request time, environment, and any error or trace ID before contacting support.

Read the trace-tag reference for request examples.