Search job fails and returns an error

Users should retry their request if their search fails and returns the error "Search ID not found. The search may have been cancelled while there are still subscribers".

If your search job fails and you get an error indicating that the search might have been cancelled while there are still subscribers, your request has most likely encountered a lag or glitch across your network connection that interfered with the processing of your request. This issue happens sometimes with responses to Internet requests and isn't unique to Splunk software.

There could be several reasons why you might be getting this error during searches, such as:

  • The job status file was created and written, but there is a system delay flushing it into the file system.
  • The search request is queued, but not dispatched, possibly because the job status file was not created before dispatching.

Symptom

Your search job fails and the Search app returns the following error: Search ID not found. The search may have been cancelled while there are still subscribers.

Remedy

If you get this error, retry your request. For example, wait a few moments and resubmit your HTTP request in your Web browser.