"message" : "Job ID is invalid."

Follow

Klaus Nji

• November 05, 2016 14:52

I submit a search job and get back the job ID in the location URL as indicated in the response. For example, I get something like this back: https://api.us2.sumologic.com/api/v1/search/jobs/566671A4A7BC1458 When I immediately query that response back details of the result, I get { "status" : 404, "id" : "819OC-CHUM5-34PDW", "code" : "searchjob.jobid.invalid", "message" : "Job ID is invalid." } This is happening with all of my search requests. What am I missing now?

0

• 

  Patrick Walters

  • December 29, 2016 00:03

  For what its worth, I also see this. I submit the GET JOB and get "Job ID is invalid." many times, but ocassionally it will work and even when it does a subsequent GET JOBID/messages fails with "Job ID is invalid." Very odd API behavior.

  0

  Comment actions Permalink
• 

  Steve Dunlop

  • March 16, 2017 14:37

  Hi Patrick and Klaus,Did you ever find a solution to this? I am seeing the exact same behaviour.Thanks.

  0

  Comment actions Permalink
• 

  Patrick Walters

  • March 16, 2017 19:45

  Nope, I gave up... Seems to be no @Sumo API sumo logic presence in this forum either.

  0

  Comment actions Permalink
• 

  Mario Sanchez

  • March 16, 2017 22:14

  @Klaus Nji, @Patrick Walters, and @Steve Dunlop, My colleague @Frank Reno pointed out that cookies are required in order for subsequent requests to work. Check out: http://help.sumologic.com/APIs/02Search_Job_API/About_the_Search_Job_API In particular: "Cookies must be enabled for subsequent requests to the search job. A 404 status (Page Not Found) on a follow-up request indicates that a cookie did not accompany the request." Let me know if this resolves your issue. Cheers, Mario

  0

  Comment actions Permalink
• 

  Steve Dunlop

  • March 17, 2017 14:39

  Hi Mario, many thanks for the answer. Adding cookie handling fixed the issue and it now works!Please note that the error message is "Job ID is invalid" ... nothing to do with cookies!! Please can you update the documentation (or the API error code) so that others don't have to waste time on this.Thanks!

  0

  Comment actions Permalink
• 

  Mario Sanchez

  • March 17, 2017 23:41

  Thanks Steve. Already logged a request to improve the error code. Cheers!Mario

  0

  Comment actions Permalink

Please sign in to leave a comment.