Assistants API: Resolving the 'No run found with id' Error When Checking Run Status

Below is some guidance based on the Assistant UI API documentation for troubleshooting this issue.

Verify the Run ID Source

Make sure the run ID you are storing is exactly the one returned when you initiate the run (for example, via the startRun function). Even a small discrepancy or using a stale value could lead to the error “No run found with id.”

Tie Run to Its Thread

In our API, runs are managed in the context of a thread (that is, a conversation or a message stream). When checking the status, verify that you are using the correct thread context along with the run ID if required. In some instances, the run is associated uniquely with a thread so that missing or mismatched parent information might cause the API to not locate your run.

Run Lifecycle Considerations

Keep in mind the lifecycle of a run. At the moment of creation the status is “queued,” but once the run has been processed (completed, cancelled, or expired) it may no longer be available for further status queries. If you check the status too late, the run might have been removed or updated to a state that no longer supports retrieval.

Troubleshooting Steps

1. Confirm the Returned Run ID:
   Verify in your API call logic that you capture and store the run ID immediately after invoking the startRun method or equivalent function.

2. Check Thread Context:
   If your application utilizes thread IDs, ensure that your status-check API call references the correct thread so it can locate the run.

3. Review Timing:
   If there is significant delay between run creation and status check, consider whether the run might have advanced past “queued” and been cleaned up or expired – which can also result in the “No run found with id” error.

4. Logs and API Responses:
   Use logging around the API call to retrieve the run status to make sure that the run ID passed in is the same as returned by the creation call.

Example Outline

Here’s a simplified outline that shows how a run might be created and its status checked within the thread context (based on our API’s example code):

TYPESCRIPTCopied
// Start a new run, capturing the run ID
const threadId = /* create or get thread id */;
startRun(threadId); // Internally returns a run id which is stored

// Later, to check the status of the run:
const runId = /* retrieved run id from your database */;
const status = await getRunStatus(threadId, runId);
if (!status) {
  console.error("No run found with id", runId);
}

Ensure that the logic retrieving and using the run ID aligns with how the API expects it to be used.

Summary

The “No run found with id” error typically means that the run ID being referenced was either never correctly created with the right thread context, has expired, or was mismatched in subsequent API calls. Double-check your thread and timing details to ensure you’re querying an active run.

If you continue to face issues, verifying your implementation against the latest documentation may help clarify any nuances in how run IDs are handled within the framework.