Jenefer-Monroe
commented
2 weeks ago Hello. The flow one failed because the Maker one failed and it cannot find Makers that were to be inserted by it.
So you will need to back up and delete refresh history to before these failures once resolved.
It sounds like the dataflow could not access the AAD table.
This could be because they missed a spot they needed to create a connection, or it could be something wrong with your environment.
Please open the Maker dataflow and click each query, waiting for it to resolve all the way to the bottom, to see where the failure occurs.
For example click Makers, then wait till it resolves all the way to the last action (change)
Then click App Makers and wait, etc
abhijkumar-msft
Does this bug already exist in our backlog?
Describe the issue
Hi team,
We're seeing the following data flow errors occur after having the client upgrade to the latest release of the CoE Starter Kit:
Flows Data Flow:
Makers Data Flow:
Latest Errors:
Quick FAQ / Debugging Steps: The "next refresh" is only set for makers. Yes; verified with the client that the "next refresh" is set only for Makers. What information is given about the failures for flow. _The detailed errors are provided in the initial snapshots in the ticket description (Flows Data Flow and Makers Data Flow).
Expected Behavior
The data flows should run as expected and not error out randomly.
What solution are you experiencing the issue with?
Core
What solution version are you using?
April Release
What app or flow are you having the issue with?
Sync Data Flows
What method are you using to get inventory and telemetry?
Data Export
Steps To Reproduce
Install the latest version of the CoE Starter Kit and allow it to run during it's pre-scheduled times.
Anything else?
No response
AB#3239