So, here's the deal. I'm trying to use Flow to build a chatbot integration (simple webhook that kicks off several Switch options with a number of calls to CDS [create, update, list, get - the usual!).
Now here is the kick - I've optimised the flow to the absolute maximum (no unnecessary variables, response before action etc.) but I do have to get a response to my request in 5 SECONDS. If my webhook service doesn't respond in 5 seconds my chatbot will stop responding to the user - NOT A GOOD LOOK.
The good news is, about 80% of the time it will work all fine (see attached screenshot). However, every now and again the flow will just get stuck on ANY CDS action for 20-30+ seconds at a time. There is no logic to it - however, it does seem to happen more often if it is the first connection to the CDS (in any given time period).
Anything I can do here? Or should I just accept that CDS will always be unreliable when it comes to instant connectivity and think about storing my user data in a "leaner" DB?
Thanks for replying. Reposted this now in Flow area.
To answer your question - please find attached. I can go into more details but this is an intermittent failure, it does work more than half the time than it doesn't. My question is really more about the general latency of Flow & CDS actions than anything more specific.