Today I hit one of those unclear error messages in Power Automate. All I got was Flowname.Run failed: _scrubbedSensitiveData_. What does that mean?
The setup
Table of Contents
Today, in my app, I was calling a flow from the ultimate Power Apps user guide and this had been working for a few days and then suddenly while I was enhancing my flow further I got this weird _scrubbedSensitiveData_ error.
It wasn’t until I reviewed the connections that I found the cause of the problem.
One of the changes that I had made to my flow is that I added an additional step calling an Azure Runbook. My flow already had an action that called the an Azure Runbook action, however this new action seems to have added an additional connection to my flow.
Fixing the _scrubbedSensitiveData_ error
Where my Create Job action is using one connection reference:
My Get Job Output is using a different Connection reference. It would be nice if Power Automate could always default to use the connection reference that was used by other steps in the same flow.
Once I switched the connection reference of the added step to be the same as the original action problem was resolved.
Some more thoughts
Does this mean that I can’t have 2 connection references set up for an app? No absolutely not!
The problem here is that I added the flow to my app with a single connection. Then as the connections within my flow changed, the app wasn’t aware of these connections yet. So reconnecting the flow would have fixed the issue as well, however it is better to keep the number of connection references to the minimum where possible.
There are a number of different reasons why you might get this same error however as far as I’m aware the _scrubbedSensitiveData_ always has something to do with invalid or incorrect connections.
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Are there any best practices or strategies you’d recommend for managing connections in Power Automate to avoid or quickly resolve issues like the “scrubbedSensitiveData” error?
In general following best practices. Having at least 3 environments (dev, test, production) setup avoids a lot of problems. And of course every apps and flow needs to be part of a larger solution package that is deployable.