Greetings Eduardo:
If your situation applies to voice interactions, I would also recommend voting for & following this enhancement idea. Its premise is to allow admins to identify/catch the error/status code and subsequently take a custom course of action based on the error/status code (e.g. play a message, set a variable, loop, transfer the call, etc.) That's what we are able to do for messaging, bot, & digital flows, and were surprised to see the lack of parity in voice flows so we can do the same thing there.
------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology | Colossians 3:23-24
------------------------------
Original Message:
Sent: 02-16-2026 16:31
From: Eduardo Ortiz
Subject: How to handle exceptions when invoking a Data Action in Architect?
I have a Data Action that calls an external API. When the API returns an error (like 404 or timeout), the flow goes straight to the generic error path.
What's the best way to catch those errors and return a custom message to the caller in Architect?
#Architect
------------------------------
Eduardo Ortiz
Sistemas
------------------------------