Dataflow fails in Pipeline with another user's credentials

[Thorns]

I have a pipeline that starts multiple dataflows in the morning.  All of them run successfully except for one.  All of the dataflows, except for the one that fails, are owned by myself and have my credentials.  The one that is failing has my co-worker's credentials.  Is there an issue with running a dataflow in a pipeline where the dataflow is owned by another user?  How can we work around this?

Here is the failure message.

Dataflow refresh job failed with status: Failed. Failure reason: { requestId: b303e54d-55f9-4c98-a365-18538f1960f6, errorCode: EntityUserFailure, message: Something went wrong, please try again later. If the error persists, please contact support. }

[tayloramy]

Hi @Thorns, 

@nielsvdc is completely correct. I recommend having items owned by either service principals, or service accounts for items that do not support service principals for anything in production to prevent these errors. THis also ensures a smooth transition if someone leaves your org. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[Thorns]

Would service accounts not have the same problem since it's just another "user"?

[nielsvdc · Accepted solution]

Hi @Thorns,

When a pipeline runs, it uses the identity of the user who triggers it. If the dataflow was created or last authenticated your co-worker, and you don’t have valid credentials for its data sources, the refresh fails with EntityUserFailure.

To solve it, you might want to take ownership of the dataflow, edit the dataflow and refresh the connection credentials with you own credentials.

Depending on the connection types within the dataflow, you might want to consider using service principal or workspace identity authentication in the connection. This works independently of user accounts.

Hope this helps. If so, please give a Kudos 👍 and mark as Accepted Solution ✔️.

[Thorns]

We were considering transitioning to service principles, but this makes it a higher priority now.  Thank you for the information!