Pipeline Failed to load with Job ID not found

[TGTun]

We encountered issue with our scheduled artifact jobs in Microsoft Fabric from Aug 25 2025 6 PM SGT to Aug 26 2025 4 AM SGT. Also, tried out manual triggered the job and the same error as below. We have checked with network team and they replied there is no problems logged and everything is good at that time. Where can we check if this kind of issue is happened again ? 

Thanks in advance.

TG

[v-prasare · Accepted solution]

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[TGTun]

Sorry for my delay reply. We noticed that there was service disruption at that moment. It's working back again after few hours. 

[v-prasare]

Hi @TGTun ,We would like to confirm if our community members answer resolves your query or if you need further help. If this issue blocking you, please consider raising a support ticket for further assistance.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

@shashiPaul1570_ , thanks for your prompt response 

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are

@TGTun

[shashiPaul1570_]

Hi @TGTun 

This error usually occurs when the pipeline run record cannot be retrieved in Fabric — either because the Job ID reference expired, or there was a transient service issue at the time of execution. Since your network team confirmed no issues, it’s most likely related to Fabric’s backend job metadata not syncing correctly.

Steps to confirm 

Check the Pipeline run history in Fabric → Data Pipelines → Monitor tab → verify if the Job ID exists.

Review the Capacity Metrics App for any outages or throttling around that timestamp.

If the problem persists or recurs, raise a Microsoft Support ticket with the exact run ID and timeframe so they can check backend logs.

Please follow this link for more details
https://community.fabric.microsoft.com/t5/Data-Pipeline/Error-Job-ID-not-found-or-expired/m-p/467709...

This is typically a transient error and should not impact future runs once the service stabilizes.

Hope this helps! 🙌 If it does, please give a Kudos 👍 and mark as Accepted Solution ✅ so others can benefit.

Best regards,
Shashi Paul