For one of our flows while testing we realized it was not getting triggered.
We could see it giving below error –
There’s a problem that needs to be fixed to trigger this flow – It hasn’t been triggered successfully in the last 28 days.
We tried a couple of things and I think either switching it on and off and/or updating the trigger condition and saving it temporarily seems to have fixed the issue. Either of these would have created the correct corresponding Callback registration records.
Suppose we have below array variable – varTestVariable having a list of GUIDs in it.
And we have another array variable varWorkOrderGuidToBeRemoved which has the list of GUIDs we want to remove from our first variable varTestVariable
For this, we can make use of the Filter array action
In From, first we have specified the array variable from which we want to remove the values, followed by the variable that holds the values to be removed. Next, we have specified the “does not contain” operator and finally specified the item()
We can also click on Edit in advanced mode to see or edit the expression.
We can use the Body of the Filter array action that will hold the result in subsequent actions.
On running the flow, we can see that the values that existed in the second array variable were removed from the first array variable.
Recently we had to change the password of the user account being used as an owner of the cloud flows as well as the used for connection/connection reference.
So we tried it on a trial environment first, below is our flow that runs every 5 minutes and creates a contact record (Dataverse), sends an email (Office 365 Outlook), and creates a file (SharePoint) owned by the same account along with the connection reference.
Below is our cloud flow
We can see the details around Connection References and Owner. We can also see it running successfully getting triggered after every 5 minutes.
Now let us update the password of the account that is being used in the flow.
Interestingly after password change our Flow kept running successfully without any errors.
Contact records are created in the Dataverse.
Mail sent using the Send an email action.
Files getting uploaded using the Create file action of SharePoint.
Also, we see the status of the connections showing as Connected.
It could be because Power Automate might be using cached credentials for a certain period after the password change, and/or the connections that use the refresh tokens to maintain authentication, have their tokens still valid.
Here what we can do immediately after changing the password is open the connections and click on Switch Account, sign in again using that account. That will referesh the connection.
That is exactly what we did for our Prod and other environments after we updated the password and we didn’t face connection failed issues or any other error for all our exiting flows.
We recently got the below error in one of our cloud flows, the requirement was to fetch the distinct work orders that have notes with attachments associated with them.
A resource of type ‘Microsoft.Dynamics.CRM.annotation’ was found in a resource set that otherwise has entries of type Microsoft.Dynamics.CRM.msdyn_workorder’. In OData, all entries in a resource set must have a common base type.
This occurs if we try using the aggeration in the Fetch XML queries in the List rows action.
The solution was to rewrite the fetch xml query without using aggregation.
And then next if we want to get the distinct values, we can use the Union function for that.
Here,
we are first adding the GUIDs to the varLstWorkOrderGUID array variable using Append to array variable action
And then applying the Union function – to remove the duplicate from the array.
Recently while trying to open one of our cloud flows we got the below error.
Error: The XRM workflow table row could not be found.
Inside the Power Automate maker portal for the new designer, we got the below error
We could see our flows were in the OFF status.
We switched ON the flows, and this fixed the issue for us.
We were able to edit our flow then.
As we recently restored the environment (was deleted), because of which the corresponding ‘Callback Registration’ records might be incorrect or missing. So enabling the flows would have created new entries in the Callback registration records for our flows, which fixed the error.
Nishant Rana's Weblog 