Without an easy capability to view logs for a call that experiences as an error. I'm finding it taking forever to debug callflows.
The official debug tool is tedious and takes a very long time to get through to the point of failure.. And if you zone out on the endless stream of TTS you miss it ... Listening to a call 3 times could take nearly an hour..
(Hint this is not accessible to many people with neurodiversities such as ADHD and ASD - and yes I'm one of them)
So - Is there a tool that can be used to get a text breakdown of what happens in test call .. (vis a vis logs that show what function was incorrectly implemented and why - like MCP (ORS/GVP) or IRD ?
A proper debugging tool would be even better.. Eg. export the code and import into said tool, and define break points and simulation data etc..
First the hack: use the Set Participant Data action. Sprinkle it anywhere in your flow that you want to know you got to an action and/or what the value of something is. After the flow ends, you can look up the conversation with the api and see all the data you wrote out.
The good news: we are working on a proper debugger. It will be awesome.
The bad news: it's still in development, targeting a beta by the end of the year. If you want to be part of the beta, contact @JustinCampbell. Until then use the hack above.
Thanks for the suggestion of using the API. ..We are scrambling a build together for our first launch in a couple of weeks. Even though we could build a straight hard coded flow, as both lead engineer and solution architect, I've set the principles to build data driven, scalable and supportable (by the clients in-house team). So flows are driven by tables and then CRM/billing system data once the API layers are available at the client end.
The migration is for a fairly mature Engage platform customer.. Needless to say, I'm quite busy... Unfortunately, I had to design for a support team that is not comfortable yet, with doing things from API's..
I'll be able to get something setup for myself when I have a moment to breathe, but will be longer before I can train my team.
I'll definitely be in contact about the beta... I was sure I couldn't have been the first person to raise this deficiency...
@AllanK I have been asked about this a few times and even in my flows i find it easiest to use the GC Chat room webhook to log in the messages in realtime into the room I documented this here: https://github.com/mcphee11/architect-logging while I agree the new feature will be best for now i still use this logging method.
Thanks for this. Were fighting to work out an issue all day.. (syntax of course, which TTS doesn't convey)...
We're going to stuff it into a common module with a set of standard inputs.
Debug tools would be better when you don't know where you are looking (And haven't inserted lots of these yet)
but in potentially common failure points, like data tables this could be a great production notification tool..