Bot Flow transition failure during variable assignment in ARCHITECT

Architect & Flows
1

Hi all,

The current environment is a multi-tier IVR hosted on Genesys Cloud in the London region. We’re attempting to pass complex state data from a Digital Bot Flow into a primary ARCHITECT flow.

The intended logic flow is as follows:

[ Digital Bot Flow ] → ( Set Variable ) → [ Transfer to Architect Flow ] → ( Update Variable ) → [ Queue ]

We’ve configured the BOT FLOW to pass a custom string containing a customer ID and a priority flag. However, the transition is failing intermittently. The interaction drops entirely without hitting the queue, and the interaction ID disappears from the view.

To debug this, we’ve attempted to force higher logging for the specific flow instance using the API.

POST /api/v2/flows/{flowId}/instances/settings/loglevels

The request was sent as:

{
 "logLevel": "DEBUG"
}

Despite this, the logs are returning empty for the transition period. There’s no trace of the variable assignment failing or a specific error code in the flow output. The BOT FLOW thinks the transfer was successful, but the ARCHITECT flow never triggers the entry point.

We’ve checked the VARIABLE names for case sensitivity and confirmed they match exactly between the Bot and the Inbound Flow. The issue persists across different test accounts.

2

purecloud-platform-client-sdk doesn’t magically sync bot_variable state during the handoff if the types aren’t an exact match. It’s a classic failure where the Transfer to Architect Flow action drops the payload. Check GET /api/v2/analytics/botflows/{botFlowId}/sessions to see if the session actually persisted the value before the jump.

2 Likes
3

Fun one today. Think of the variable handoff as a luggage carousel- if the bag doesn’t match the tag exactly, the system won’t release it to the next person. It’s usually a type mismatch between the Bot and Architect.

Check the JSON structure in the Bot Flow. If it’s a string but Architect expects a number, it’ll fail. Try casting everything to a string first:

{
 "bot_variable_1": "12345"
}
4

That’s right, and it’s a nightmare when the types drift. The documentation-and I quote-states “Variables must be defined in both the bot flow and the architect flow to be passed.” If the BOT FLOW uses a string but ARCHITECT expects a number, it fails. Use the ADMIN UI to verify the VARIABLE TYPE on both sides.