Sky API to Check Query Job Status - Failing with a NOT FOUND even though it has correct ID

Kristi Hill

Hi — A newbie when it comes to the SKY API and this has to be a typo or a syntax error on my part. I've watched videos and used all of the suggestions I can find — but it fails. (I’ve uploaded a screenshot of both of the components in question.)

I've got a DELAY set up to check to see if the query has completed, so that I can then export the data from the query.

If I look at the RUN QUERY HTTP that I set up, the body comes back with :

{  "id": "2388a948-3940-4b24-aec4-ed99f8fdb951",  "status": "Pending"}

The RELATIVE PATH being displayed in the DELAY portion that is checking to see if the job is completed is:

/query/jobs/2388a948-3940-4b24-aec4-ed99f8fdb951

So the ID matches from the actual RUN to the CHECK STATUS, but the error is always "not found". That leads me to believe that it must be some sort of syntax issue on my end, but I'm just not seeing it…

Any ideas?

Crystal Bruce

Hi @Kristi Hill thank you for posting! I'm checking with my team on this.

Rebecca Sundquist

@Kristi Hill , I know you said "The RELATIVE PATH being displayed in the DELAY portion that is checking to see if the job is completed is: /query/jobs/2388a948-3940-4b24-aec4-ed99f8fdb951" and this looks right,

but the screen shot shows that CheckStatusHTTPS is using relative path: "/query/jobs/id:2388a948-3940-4b24-aec4-ed99f8fdb951". Have you tried without "id:" in that relative path?

A second way to troubleshoot is to use SKY API Console to test the endpoint with the job ID from the RUN QUERY HTTP action: API Reference - Query execution job status. This will tell you whether it is an issue with the job ID or, if successful, suggests the Power Automate action is the failure point.