Incorrect Fabric pipeline status from the API

[Konstantin_K]

Why does this endpoint return Failed status for the pipeline when it's actually NotStarted?

Why not NotFound, Unknown or NotAvailable at least?

It doesn't make any sense.

[v-dineshya]

Hi @Konstantin_K ,

Thank you for reaching out to the Microsoft Community Forum.

When you start a Fabric pipeline job instance via the REST API, there’s a short window where the run metadata hasn’t propagated to all back‑end services yet. If you immediately ask another endpoint for the run’s status, that lookup can return NotFound even though the run exists and is about to start. The endpoint you are calling then wraps that NotFound lookup error into a “request failed” result for the job instance you are inspecting. It is the API call failed, not the pipeline run.

Please refer below link.

Solved: Job Instance API returning inconsistent and incorr... - Microsoft Fabric Community

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

[Konstantin_K]

Hi, thanks for the response.

> The endpoint you are calling then wraps that NotFound lookup error into a “request failed”

But why? That's incorrect. The request is not failed. Not found is a valid response. Why wrapping it?

> It is the API call failed, not the pipeline run

That's a dedicated model for the pipeline run. This status field reflects the status of the pipeline run. Why the API response status is in the pipeline run status property? Here's a screenshot from the documentation.

What you're saying contradicts the documentation.

[v-dineshya]

Hi @Konstantin_K ,

Thank you for the update.  It appears this issue might require deeper investigation from the Microsoft  Fabric support team. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Regards,

Dinesh

[v-dineshya]

Hi @Konstantin_K ,

We are following up to inquire whether you have raised the support ticket. If you have already done so, we kindly request you to share your feedback regarding the issue raised.In case a solution has been provided, we would be grateful if you could share it with the community. This will assist others facing similar challenges and benefit the wider community. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.

Regards,

Dinesh

[Konstantin_K]

Hello @deborshi_nag,

Thanks for the response, but I don't see how it's related to the initual question.

The problem is that the endpoint returns wrong status.

It returns `Failed` when pipeline run is not failed.

There's a huge difference between `NotFound` and `Failed`.

It happens right after I start the pipeline run.

After some time it starts to return proper values.

[deborshi_nag]

That could happen if the parameters/GUIDs supplied were missing or incorrect, since you're doing it programatically - hence asked you to try it online. 

[Konstantin_K]

Parameters were not missing or incorrect. The same exact request returns NotStarted after some wait.

If I do that from UI, this wait will be there, because I will need to copy-paste headers and parameters manually.

But I need to thad inside the application, not in the UI.

You can just try it yourself, but not from UI — create a pipeline run and query the status right away.

[Konstantin_K]

And anyway the initial question is still the same. Even if the parameters are incorrect, why the status is Failed, when it should be NotFound according to the error message? 

[deborshi_nag]

I could be missing something, but when I tried the REST endpoint on my pipeline I could see the same statuses, difference being on Fabric Monitor the status shows Succeeded, but the REST API returns Completed. This is in-line with the ItemJobStatus values. 

[Konstantin_K]

You're answering to some other question, that nobody asked. I'm repeating same for the third time. Why when the response is that pipeline not found, the status is failed? It's wrong, misleading, forces to create crutches in the code and doesn't make any sense. I'm not asking why it is not found.

Take a look at my screenshot, please.

What does the message in the failure reason say? Does it say that the pipeline run failed? No. Why the status is failed then? Not found != failed. 

[deborshi_nag]

Hello @Konstantin_K 

Have you tried it online using the [ Try It ] button or is it that you can only try is programmatically? You can also check with the "Job Scheduler - List Item Job Instances" REST API that returns all job run instances with their associated run status. 

Job Scheduler - List Item Job Instances - REST API (Core) | Microsoft Learn