Fabric Data Pipeline fails with "LSROBOTokenFailure" error

[Anonymous]

Previously my PL was running without this error.

{
"RunId": "2b0842be-506a-4811-b7dc-a7e863382796",
"IsCompleted": false,
"EntityName": null,
"Status": "Fail",
"FailureType": "UserError",
"Message": "BadRequest Error fetching pipeline default identity userToken, response content: {\n \"code\": \"LSROBOTokenFailure\",\n \"message\": \"AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '2024-06-06T23:11:27.0960837Z' and the TokensValidFrom date (before which tokens are not valid) for this user is '2024-06-11T10:38:53.0000000Z'. .........

Im not aware of any password changes etc. I also recreated the PL in stages and it seemed to work ok until I included an Invoke PL activity for an exisitng PL and the failure moved and occured on that Invoke PL Activity.

Any help solving this appreciated.

[deshtehari]

It's almost a year past from the original report, and still no contribution from the Fabric team!

@Anonymous Can you unmark the workaround as a solution.

[Liszet]

This is still an issue as of 2025-06-06. We have a colleague that quit and a pipeline was still failing even though the connections were in order. I had to make a small edit and save in order for the pipeline to work again.

[scone]

I love you 💓

[AaronWong]

As of 2025-06-03 this is still an issue.

[kk1234]

I cannot find the solution here

[Anonymous · Accepted solution]

It seems "tickling" and saving the PL by a minor edit solves the issue.

[Zall]

We ran into this issue last weekend as well. 

While making any change to the pipeline fixes this we strongly suspect that the issue itselfs originates from someone who made change to either the pipeline itself or any activity itside it that had their account deactivated or access rewoked.
One of our colleagues ended last week and all the pipelines that he partially worked on suffered from this issue while everything else went through fine.

[Cobra77]

it worked for me too , thanks , but this is not practical with many pipelines to rework

[Thania]

ok. Thank you.  But I have various pipeline and it is difficult to enter each one 😞  I will hope that support solvents it of another way.

[darrend]

Thanks for contributing. Very helpful. Solved my problem. 🥳

[Courch]

Encountered the same issue and tried different solutions for hours before reading your post.

Added a minor change, saved and evething's back to normal.

Thanks for the tips.

[Anonymous]

Hi @Anonymous 
Glad that your query got resolved. Please continue using Fabric Community for any help regarding your queries.

[Anonymous]

It is still a bug in my view so will this be investigated? A work arround is not a solution.