Error in Flow designer -- "Cancelled : error="Failed to get plan from instance for context: 1a3d25eea0054410da5ab492bf42b2aa"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2019 10:34 PM
Hi ,
I am using flow designer for my automation and i created a flow and subflow for it.
When i am submitting a request it is working till check and as it calls a subflow it is giving error-"
Cancelled : error="Failed to get plan from instance for context: 1a3d25eea0054410da5ab492bf42b2aa".
Thanks in advance,
"
- Labels:
-
flow designer
- 5,635 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2020 03:35 AM
I'm still struggling with this months later. It happens around 1% of the time so not huge but still not ideal. The biggest problem we have is that we can't manually replicate the issue. So when i'm running tests using the same scenario of the failed flows, it then works.
Is anyone able to replicate this issue manually? If so, how? This would be a huge help in getting to the bottom of it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2020 08:21 AM
Is it anything to do with who you're running it as? I've started getting similar issues in New York but never had them in London where it didn't have this functionality.
Thanks,
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2020 06:35 AM
We were able to resolve our issues, it looks like they were due to known bugs. Not sure if they are similar to what you are experiencing but we are also on New York.
One was an issue where we had to convert service catalog variable data pills to String type if using them in conditional statements (we did the conversion in a custom action and then returned them to the Flow). The other we had to put in a 30-second timer delay when running an IntegrationHub step on the MID server if it was immediately following an approval action.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2020 07:32 AM
Thanks Steve, I'll try this and see if it resolves our issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 03:25 AM
Hi I have similar error
Cancelled : error="Failed to update plan context: e4bbdcd94b4314901110017917cea727 from MID"
running a flow to login to an API but getting this error, was working before.