I have a large flow that, up until I left work yesterday, worked flawlessly. However, suddenly it started duplicating itself whenever a response was submitted to a Form. Additionally, when I started troubleshooting, I discovered that the action "Get response details" no longer had the "Response ID" dynamic action, and it was instead changed to "List of response notifications Response ID". When I try to use that content, it switches to an "Apply to each" loop, where I am still unable to get the response ID from the Form. I use the response ID as a key field when recording the data submitted by the form.
I made a new Flow, just to try and see where the issue is, and it doesn't seem to lie with the Form, as the test Flow works as intended.
What could have happened, and what are my options to fix this?
UPDATE: It looks like there was a problem with the Split On setting. I'm not sure how it changed, but the array was set to triggerBody()?['data/value'], when it should have been triggerOutputs()?['data/value']. Exporting the Flow, changing the spliton setting in definitions.json, and the updating the existing flow corrected the problem with the "Get response details" action.
Solved! Go to Solution.
Awesome, thanks for posting the fix as an update. Re-posting here in case anyone just wants the solution
@stavi82 wrote:UPDATE: It looks like there was a problem with the Split On setting. I'm not sure how it changed, but the array was set to triggerBody()?['data/value'], when it should have been triggerOutputs()?['data/value']. Exporting the Flow, changing the spliton setting in definitions.json, and the updating the existing flow corrected the problem with the "Get response details" action.
@iAm_ManCat |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
Awesome, thanks for posting the fix as an update. Re-posting here in case anyone just wants the solution
@stavi82 wrote:UPDATE: It looks like there was a problem with the Split On setting. I'm not sure how it changed, but the array was set to triggerBody()?['data/value'], when it should have been triggerOutputs()?['data/value']. Exporting the Flow, changing the spliton setting in definitions.json, and the updating the existing flow corrected the problem with the "Get response details" action.
@iAm_ManCat |
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you! |
Thanks! |
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
12 | |
11 | |
10 | |
9 | |
6 |
User | Count |
---|---|
26 | |
20 | |
12 | |
10 | |
7 |