Error - Job ID not found or expired

[vivien57]

Hello everyone,

Since this morning I ha ve been getting this error when I try to launch a Fabric pipeline. Have you already had this error? Is this a known error?

When I launch the pipeline, it runs like this for a few minutes (without launching it) and then it ends with the above error

Thank you in advance for your feedback

Have a nice day,

Vivien

[Juriaan-007]

This seems still an issue. Is there an update on scheduled runs where the pipeline id is missing?

[vivien57 · Accepted solution]

[KevinFeit]

Is anyone still getting this error today?  We have a scheduled pipeline that runs nightly at 4:00 AM Eastern and the scheduled run has failed since Saturday.  Clicking on it in Monitor shows "Job ID not found or expired". Rerunning it manually works fine.

[echaintreau]

On our side Microsoft push a change between Monday the 28th and Tuesday the 29th and all our pipeline work again after this change.

Hope it also fix the issue for you

Sincerely,

[vivien57]

Fabric-specific incident (in addition to the Power BI incident with dataset refreshes)

[v-nmadadi-msft]

Hi @vivien57 ,
Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious. 

Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you

[vivien57]

It's official

[carlossoria]

Same problem here, every scheduled pipeline failed in today's execution

[amaaiia]

Same issue here, we have a scheduled Data pipeline in PRODUCTION calling some invoke Pipeline activities. These activities failed due to Job id not found, and we've seen the invoked pipelines have been executed 3 hours later...

Also, the UI is taking too long to load the interfaces in Fabric.

Something is going wrong in Fabric.

[rauttu]

One of our Fabric enviroments has exactly the same, this started between presumably 22 - 23 CET last night (based on our executions and how they have been running). From around that time the job scheduler of Fabric has become unusably slow it seems, executions get started hours after their intended schedules and this error "Job ID not found or expired" is visible in their execution as an error. Some of them remain in "Not Started" state even though the execution has hit this error. Happens with pipelines invoking other pipelines at least.

Another note is that the git interface of Fabric is experiencing severe slowness within this same environment. Making acommit took 30 minutes - normally happens in seconds.

[Tröttöröö]

Same issue. Scheduled and manual runs both not working.

[Cookistador]

Same impact on semantic models

The refresh is not triggered, 

scheduled or on-demand refrehses are not working

[Kuzavas]

I'm facing same problem from this morning:
"Job ID not found.."

Pipelines not running as it should..

[Anonymous]

I have exactly the same problem.
I only replied to escalate the thread.

[Anonymous]

Update: We have had this problem for a few days now. I have just tried to update a pipeline again as a test and was fortunately able to determine that the error no longer occurred. I also tested scheduled executions, which also worked again.

We are continuing to monitor the behavior.
Repeat your tests again.

[Arundhati_Sen1]

I am also facing the same issue, pipeline execution is stuck and nothing is coming in Monitor Screen.

If I try to rerun pipeline from monitor screen then getting Job ID not found error.

[echaintreau]

Hello @vivien57,@Cookistador 

I am also facing the same issue here all our pipeline using the invoke pipeline or notebook launcher seem to failed also the same for PBI dataset refresh. all of that this morning.

I assume the error is located in the API call done by Fabric, where the ID is not correct.

[Cookistador]

Hello @vivien57 

I'm also facing an issue with the data pipeline since this morning

I made a very basic flow, when I run it, I got a confirmation message

But if I had a look in the pipeline history, I did not see any flows

And it is the same in the monitor

So maybe an issue with the service ?

[vivien57]

Isn't there a link with this known problem? We're talking about a refresh dataset here, but isn't that more general?