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,641 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 07:22 AM
We're getting loads of these, all on different flows that also call API's, but not on every flow. According to this https://hi.service-now.com/kb_view.do?sysparm_article=KB0827240 it's caused by a network error between your instance and you mid server . I think if there's a blip in the network when one of the flows is doing something it fails.
I've got my network team monitoring it to see if there's a problem.
I'm going to restart the mid servers tonight to see if it helps, but don't think it will.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 07:55 AM
Thanks Andrew. Wierdly enough a few minutes later it started working again and not seen the error again.
Phewwww.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 07:59 AM
Mine seems to be random, some days I get 1 or 2, over lunch today I got over 100. I've set up a notification to myself if the state changes to error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 11:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2021 07:09 AM
Our case not used AD, so it might be not related to the same, but eventually the network can cause such problems... We need to think of retry possibilities... in Flow, but really difficult to predict how to do it ... b/c it might be happened in any nut of the chain.