Handbook

Building Genesys Cloud Architect flows: the advanced handbook

An advanced handbook for the people who build and look after Genesys Cloud Architect flows. It covers flow types, variables, expressions, input, prompts, data actions, routing, error handling, limits, secure flows, testing and version control, then works through an example and the failures we see most. Checked against Genesys sources on 15 November 2026.

By Dave Tidwell, Managing Director48 min read

In short

  • Architect is a bounded interpreter: design against its action, size, variable and execution data budgets from day one.
  • Make data actions targeted and small, set channel-appropriate timeouts, and never loop through a large result to find one record.
  • Configure the default error path and the action-specific failure paths, so no caller ever meets a silent disconnect.
  • Put rules in decision tables, reference data in data tables and schedules in schedule groups, not in hard-coded branches.
  • Validate, debug, replay and read Flow Insights in that order, and promote flows with Archy and a written rollback route.

01

What Architect is, and where the boundaries are

This handbook is for the people who build and look after Genesys Cloud Architect flows: flow authors, solution designers and the technical leads who review their work. It is written at build level. Every Genesys capability, limit and behaviour comes from Genesys's own documentation, listed in the sources at the end and checked on 15 November 2026. Where something is our own delivery practice rather than a Genesys statement, it is labelled QVCCS practice. Architect changes weekly, so re-check a figure against the source before you quote it to anyone.

1.1 What Architect does

Architect is Genesys Cloud's visual flow designer. Genesys describes it as a tool for linking together predefined operations to create simple or sophisticated menu applications: playing audio, routing interactions to agents, queues, voicemail, external numbers or other flows, and adding non-menu digit collection, data dips, conditional logic and expression editing.

Two consequences of that description shape everything else in this handbook. First, Architect is not a programming environment. It is a bounded interpreter with an action budget, a size budget, a memory budget and an execution data budget. Genesys states that call flows which consume excessive CPU or memory may be disabled automatically to protect system stability. Treating those budgets as design constraints, rather than as late surprises, is what separates a flow that survives years of change from one that fails quietly under load.

Second, the platform's real capability is its action library, plus data actions, plus expressions. Almost every journey that looks as though it needs custom code needs a well-designed data action and a well-chosen action instead. The few that need processing outside the flow have a documented route, which part 6 covers.

1.2 The budgets you design against

These are the four budgets that most often decide a design. Each is covered in detail later; they are gathered here because they should be on the whiteboard before the first task is drawn.

Architect's design budgets at a glance
BudgetWhat it limitsWhere it is covered
Actions10,000 actions per invocation for call, email, message and workflow flows; 400 for workitem flows; per-turn and per-session limits for bot flows.Part 10
Flow sizeA size meter per flow. At 98% you cannot publish; at the maximum you cannot save. Common modules have a lower limit.Part 10
Variables and dataA target of under 100 variables, a 32,000-character string limit and a 1,000-byte target across a bot flow handoff.Part 3
Execution dataRecording stops after 4,500 actions in call flows, values are truncated, and flows with over 350 variables drop to Base level.Part 12

1.3 Licences and the toolbox

Speech-enabled IVR and inbound voice routing are included in all four Genesys Cloud CX plans on Genesys's summarised plan comparison (dated 3 November 2026 when we checked). The toolbox itself changes with the licence: Genesys notes that the actions available in the Architect toolbox vary with your Genesys Cloud licence plan.

Build a standard flow library on the tier you intend to buy, not on the tier of whichever pilot organisation happens to be best equipped. A flow that relies on an action your production licence does not include will not survive promotion, and you will find out late. Our licence tiers guide explains how the plans differ.

02

Flow types: choosing the right container

Architect's Flows tab opens on inbound call and lists the rest: inbound message, inbound email, inbound chat, outbound call, bot flow, common module, in-queue call, in-queue email and in-queue message. The creation list is wider still, adding voicemail, secure call, workflow, web survey invite, voice survey and workitem flows. Pick the container by how the interaction arrives and whether anyone is waiting for it.

2.1 What each flow type is for

Architect flow types and their purpose
Flow typeWhat it is for
Inbound callThe main IVR entry point: answers, identifies, offers self-service and routes.
Outbound callThe flow behind outbound campaign calls.
In-queue call, email and messageThe waiting experience before an agent answers. Genesys provides a default in-queue call flow for the organisation.
Inbound message, email and chatRouting incoming digital interactions to the right queue, with automated replies where needed.
Bot and digital bot flowsConversational logic built in Architect and called from call, chat and message flows.
Secure callCapturing payment card and other sensitive details with recording and agent access prevented (part 11).
Common moduleReusable logic with typed inputs and outputs, callable from several flows and flow types (part 10).
WorkflowAsynchronous orchestration outside the interaction path.
WorkitemLogic behind work automation and task routing, with its own smaller action budget. Each worktype can have only one workitem flow.
VoicemailThe voicemail experience.
Voice survey and web survey invitePost-interaction survey journeys.

2.2 Synchronous or asynchronous: the distinction that causes rework

Call flows run inside the call path, synchronously. Email, message and workflow flows run asynchronously. Genesys is explicit that async flows have no guaranteed execution timing, may see variable latency depending on system load, and can be delayed while the platform scales up during peaks.

The causes of delay are documented too. Each action in a workflow queues a message to continue execution, so backed-up queues delay the actions that follow. If an action fails and is retried, the flow can pause for up to 90 seconds before resuming. Sequential data actions add cumulative latency, because each must complete before the next begins.

Two design rules follow from Genesys's guidance. Do not launch a large spike of flows in a short period, because the platform needs time to scale out; build load up gradually. And set expectations for async timing rather than designing as though it were guaranteed. A caller waiting on the line and a customer who sent an email an hour ago have different needs, and the flow types reflect that.

2.3 Message sending and periodic states

Message flows are subject to external rate limits on sending messages, which Genesys describes as owned by the messaging service rather than by Architect. The risk it names is the in-queue message flow's periodic state, which can send messages repeatedly. If a periodic state sends too often, you can reach those limits and messages will not go out. Set the period with the rate limits on Genesys's Developer Center limits page in front of you.

03

Tasks, states, actions and variables

This part covers the building blocks: how sequences are assembled, what counts against the action budget, and how to keep variables lean. Most structural problems in mature flows trace back to decisions made here in the first week.

3.1 Rules for tasks and states

The task and state editors are where sequences are built: flow authors drag actions from the toolbox into a sequence and configure each one in the panel beside it. Genesys documents a small number of rules that every author should know before drawing anything.

  • Most actions branch to other actions depending on your selection, then merge back to complete the sequence.
  • Some actions have outputs whose path is decided at runtime.
  • A task or state must have a closing action, such as a Success path in a Decision action, or a Disconnect action. An unclosed branch is the commonest cause of a validation error and the commonest cause of a caller meeting silence.
  • Actions can be collapsed and expanded to hide lengthy logic, and whole task or state segments can be cut, copied and deleted from the More menu.

3.2 What counts against the action budget

The action budget counts more than most authors expect. Genesys counts each entry into a menu, each menu action and each task action. Entering a task does not count as an executable action. Deeply nested menus are therefore more expensive than deep tasks, and a menu that loops back on itself for every invalid entry spends budget each time round.

Loops are the other big consumer. The Loop action can iterate over a collection, run a fixed number of times (up to 99 directly, or more through a calculated expression) or run until a condition is met, with Next Loop and Exit Loop available inside the body. Genesys calls loops a primary cause of performance problems and excessive action consumption. Where a loop is needed, keep iterations few and the body short, and ask first whether a data action could return the one item you were going to loop to find.

3.3 Built-in variables worth knowing

Built-in variables hold what the system tracks automatically, such as the caller's number or the contact list behind an outbound flow, and Genesys lists them per flow type. Three that every flow can use earn their place in most designs: Flow.IsTest, which is true when the flow is running in debug mode; Flow.StartDateTimeUTC, the start time in UTC; and Flow.Version, which belongs in any log or participant attribute you will use to diagnose a problem later.

Architect also has read-only system variables beginning Min or Max that behave as constants. System.MinDateTime, for example, is 1 January 1800 at midnight. They are useful as explicit sentinels when a date has not been set, which reads more clearly than relying on NOT_SET everywhere.

3.4 Author-defined variables: three decisions

Every variable you create carries three decisions, each documented in Genesys's guide to managing variables. Make them deliberately rather than accepting whatever the dialog shows.

  • Accessibility: available to the whole flow, or to specific tasks only. Scope down by default. A variable that only one task uses but that lives at flow scope is invisible debt.
  • Input to flow and output from flow: available on flow types that are started or called by something else, such as bot, common module, secure, workitem and workflow flows. An input's value is passed in when the flow starts; an output's value is exported when the flow ends.
  • Content is secure: marks the variable's content as secure, which changes what the platform logs and records (part 11).
  • Initial values can be a literal or a dynamic reference. Set them where it makes the flow easier to read, not by habit.

3.5 How many variables, and how big

Genesys's performance guidance gives figures to design against. Variables consume memory for the whole execution, so the count matters as much as the content.

Variable count and data size guidance from Genesys
GuidanceFigure
Target variable count per flowUnder 100 where possible; Genesys adds that fewer is better.
Automatic execution data downgradeCall flows with more than 350 variables automatically record at Base level.
General string variable limit32,000 characters.
Bot flow inputs and outputsKeep the total under 1,000 bytes, passing identifiers, flags and small context values only.
Truncation in recorded execution dataJSON 1,000 characters, strings 253 characters and collections 20 items (call and bot flows).

3.6 Consolidate related values into JSON

Genesys recommends grouping related values into a single JSON variable rather than a dozen scalars. Its own example contrasts six separate customer variables (first name, last name, email, phone, account ID and tier) with one customerContext JSON variable. The stated benefits are a lower variable count, logical grouping, easier passing of context between actions and common modules, and a single unit to manage.

The same thinking applies at the bot flow boundary. When a call, email or message flow calls a bot flow, data crosses through the bot's input and output variables. Keep that handoff to identifiers, flags and small context, and let the bot or the calling flow retrieve detail itself. Genesys explains that a large payload adds serialisation overhead at the handoff and reduces reliability, and that there is no documented maximum for bot outputs, so treat 1,000 bytes as the practical ceiling.

04

Expressions and collecting input

Expressions and input collection are where small mistakes turn into calls that misroute. Expression help is built into Architect across mathematical, statistical, text, date and time, logical, comparison, list, financial, audio, language and type-cast functions. Use it rather than recalling syntax from memory, and use the behaviours below as a review checklist.

4.1 Check NOT_SET explicitly

Genesys's own instruction is to check NOT_SET appropriately on parameters passed to function calls and to operators such as +, -, /, > and >=. A data action that returns nothing is a normal event, not an exceptional one, so design the empty path before the value path.

A related tip from the same page: when joining strings, use the Append function rather than the + operator. Genesys recommends it because Append handles NOT_SET values and is more efficient. A greeting built with + that meets an empty first name is a classic source of an expression failing in production.

4.2 Implicit casting and types

Flow authors can only assign values of like types: a string variable takes a string value. But the Architect parser evaluates the type of each expression and, where it can, reconciles the result through an implicit cast. That is convenient, and it is also why a numeric-looking account number can arrive as a string, lose its leading zeros or compare unexpectedly.

Cast deliberately wherever the type matters. Genesys documents how to convert a string value to a typed value and how it applies operator precedence, both listed under About variables and expressions. Bracket compound conditions rather than relying on precedence, because the next person to edit the flow will not have the precedence table open.

4.3 Dates, times and daylight saving

Genesys has a dedicated article on DateTime values in Architect flows and daylight saving time calculations, linked from About variables and expressions. Read it before writing any schedule, service-level or callback-window expression for a UK organisation. Flow.StartDateTimeUTC is in UTC; your opening hours are not, and for half the year the difference is an hour.

Where you can, let schedules and schedule groups do this work rather than expressions (part 7). They carry a time zone and are maintained by administrators, so the clocks changing does not require a flow change.

4.4 Validate at design time

Architect evaluates expressions at runtime, but it also validates them at design time to help authors troubleshoot. The expression editor shows error details: function names and error locations are highlighted when you select the error text. Run validation before publishing rather than finding a broken expression on a Sunday evening.

4.5 The Collect Input action

Collect Input asks a caller to enter a string of digits, such as an account number, ends input after a set count or a terminating character, and can read the entry back. Its documented settings are below.

Collect Input settings and behaviour
SettingBehaviour
No Entry TimeoutHow long the system waits for input. Default five seconds, minimum one second, maximum one minute 39 seconds.
Inter-Digit TimeoutHow long the system waits between digits before timing out.
Number of digitsAn exact count, or a range with a terminating digit.
VerificationNumeric (1234 read as one thousand two hundred and thirty-four), Individual Digits (one two three four) or No Verification.
Non-Numeric InputIf enabled, a caller may enter only * or # and the action takes the Success path. If disabled, those characters send it down the Failure path.

4.6 Behaviours that catch authors out

The action also times out when a caller enters fewer digits than specified, after the inter-digit timeout. Set the no-entry timeout with that in mind: the first digit often takes longer to arrive than the rest, especially when the caller is reading from a card.

The behaviour that surprises authors most is this one: when a call flow runs a Collect Input action, global menu DTMF and speech recognition processing are disabled. A press zero for an agent at any time escape that works on menus does not work during digit collection unless the action's own settings handle it. If your design promises an escape route during account entry, build it into that step and test it there.

Use verification for long identifiers the caller is reading out and skip it for short, obvious entries. Each readback is dead air and another chance to abandon. Collect Input has its own failure path, one of the places Architect supports action-specific handling (part 9).

4.7 Speech input settings

For speech input, two settings matter most, documented on Genesys's user input configuration. Speech Detection Sensitivity runs from 0 to 1 with a default of 0.5, where 0 is least sensitive to noise and 1 triggers on any noise. Max Speech Timeout sets the longest utterance collected; its default depends on the speech-to-text engine, and a value of zero or less means no timeout.

The documentation gives no recommended sensitivity for particular environments. Tune it on real lines with real background noise, not in a quiet office, and record the value you chose and why in the design note.

05

Prompts, languages and text to speech

Voice strategy decisions are cheap at design time and expensive after recordings have been commissioned. This part covers how Architect chooses a text-to-speech (TTS) engine and voice, how prompts and TTS interact, and what changes for multilingual and regulated flows.

5.1 Voices are set per flow and per language

TTS selection in Architect is per flow and per language, never per prompt. Genesys says so directly: you cannot set a TTS voice per prompt, because the option exists only per flow for each supported language. Engines and voices are configured in the flow's Supported Languages settings.

5.2 Which engine a flow gets

The organisation's default engine and voice are set under Admin > Account Settings > Organization Settings, in the Telephony area, with optional overrides per language. The built-in default is Genesys TTS; third-party engines come from AppFoundry and must be configured first.

How Architect resolves the TTS engine for a flow
SituationEngine used
Existing flowGenesys TTS, unless changed in the flow.
Existing flow with a newly added languageThe organisation's default engine and voice if configured, otherwise Genesys TTS.
New flowThe organisation's default engine and voice if configured, otherwise Genesys TTS.
Flow language set to NoneAny attempt to use TTS for that language in the flow produces a validation error.
  • When the organisation changes its default engine or voice, existing flows must be republished to pick it up. Plan that as a release, not a settings change.
  • At flow level you can choose a specific engine and voice, Default (which shows the resolved engine and voice) or None.
  • Genesys describes automatic fallback to the base TTS engine if a third-party service is delayed or returns errors, so test what your callers hear when that happens.

5.3 Voice and language do not have to match

A useful documented freedom: the voice need not match the flow's language. Genesys's example is a flow whose language is en-GB, for speech recognition, using an en-IE voice to suit its callers. It warns equally plainly that voices which do not directly match the flow's language can cause problems with the customer's TTS experience. If you use the freedom, test it with callers whose accents match your customer base.

5.4 Recorded prompts or text to speech

A user prompt can hold a recording or text that Architect converts to speech, per language. Where a prompt has an audio recording, Architect plays the recording for the flow's language, so Genesys's guidance is to remove the recording from a prompt when you want a TTS voice to speak it. The two mechanisms are not mixed within one prompt for one language.

Decide per prompt type which mechanism you will use before commissioning recordings. Static brand messages often suit recordings; anything containing data, such as balances, dates and reference numbers, has to be spoken by TTS or built from audio sequences. A consistent rule avoids the jarring switch between a recorded voice and a synthetic one mid-sentence.

5.5 Restrictions for regulated and government flows

Three documented restrictions matter for regulated programmes. Only PCI-certified third-party TTS solutions are available in Architect secure call flows, and Genesys names the engines allowed there. Only third-party TTS solutions are supported in the US East 2 (Ohio) FedRAMP region. And playback performance differs by language, dialect and voice, which Genesys recommends testing, with a documented procedure for third-party playback.

Genesys also offers generative voices through supported engines for call flows, bot flows and voice surveys. Treat a change of voice model as a change to the customer experience, with the same testing as a new prompt set.

5.6 Speech recognition in bot flows

Bot flow authors can choose a supported speech-to-text engine per language in voice bot flows, and Genesys automatically adds newly supported engines to the Supported Languages view in Architect. Choose the engine per language deliberately, and test it with real callers and real lines before tuning anything else.

5.7 Debug is English-only

The debug feature is available for English-only flows. Genesys warns that a flow with additional languages, or languages other than English, will not debug properly, and that every supported language on the flow must support TTS before you enable debug. For a multilingual flow, plan real end-to-end test calls into a test number instead of relying on debug alone.

06

Data actions: contracts, timeouts and design

Data actions are how a flow talks to anything outside Genesys Cloud, and Genesys calls them one of the most common sources of performance problems in flows. This part covers the contract rules, timeouts and call-site configuration, then the design principles that keep them fast.

6.1 Where data actions come from

Custom data actions are supported by a documented set of integrations, including AWS Lambda, Genesys Cloud Functions, Genesys Cloud itself, Salesforce, Microsoft Dynamics 365, Zendesk and generic web services. In the flow, the Call Data action's category is the integration's name in your organisation; you choose the data action and map variables to its inputs.

For the CRM integrations the inputs shown depend on the action chosen; a phone number lookup presents a PHONE_NUMBER field. For web services, Lambda, Functions and Genesys Cloud actions the inputs come from the request schema you created. Each integration handles phone numbers in PHONE_NUMBER searches in its own way, described in Genesys's phone number searches article. Test UK formats, including +44, a leading 0 and mobile numbers, because format assumptions break lookups.

6.2 Contract rules to write into your build standard

The input contract defines what the action is given and the output contract what it returns. Both are configured on the action's Setup > Contracts tab, in Simple or JSON form; Genesys recommends Simple. These rules come from the same page.

  • You cannot change the contracts after you publish the action. Treat a contract change as a new action plus a flow change, not a tweak.
  • Contracts do not support the $ref keyword.
  • The input contract accepts key-value pairs of string, integer, number, Boolean and null types only. It does not support nested objects.
  • Property names must start with a letter and contain only letters, numbers, hyphens or underscores.
  • Do not use the reserved names orgId, integrationId or rawRequest.
  • The output contract does not support nested arrays.

6.3 Timeouts: two settings, two purposes

There are two timeout controls, and they do different jobs. On the integration side, the execution timeout for a data action can be set between 1 and 60 seconds, defaulting to 60; when a request runs longer, the action returns a timeout response. Genesys gives the reasons as control, preventing long-running processes and reducing unnecessary concurrency.

In the flow, the Call Data action has Success, Failure and Timeout paths. The Timeout path follows when the action exceeds the default or author-specified timeout, so the customer does not wait too long, and Genesys recommends setting it no longer than 30 seconds.

On the voice path, even 30 seconds is a lost caller. Set the flow timeout from the backend's measured response times, not from the maximum allowed, and route the Timeout path to something a caller would accept, such as a short apology and a transfer.

6.4 The processing prompt

A Call Data action in a call flow can play a processing prompt during longer calls, to tell the caller the interaction has not dropped. The documented constraints are specific: it must be an audio file, because TTS is not supported; it plays once and does not repeat; and it has a one-second initial delay. Genesys's best practice is an audio file of at least 60 seconds, unless your data calls historically take much less. If yours do, the right fix is usually faster data actions rather than a longer prompt.

6.5 Response size

The largest response a Call Data action can handle is 2 MB; a larger response sends the action down its failure path. Genesys states that this limit applies in inbound email, survey invite, inbound message, inbound chat, workflow, workitem, in-queue email and in-queue message flows. Design for responses far below it in every flow type: the next section explains why size costs time.

6.6 Designing data actions that do not hurt you

Genesys's guidance is direct, and it is the section we most wish every programme had read before its pilot.

  • Targeted, not generic. Avoid one-size-fits-all actions with many inputs and outputs. Accept only what the action needs, return only the data the flow uses, and perform one well-defined operation.
  • Search on the server. Genesys contrasts an action that returns a full customer list for the flow to loop through with one that accepts a customer ID or search criteria and returns a single record.
  • Keep payloads small. Large requests and responses mean more network latency, more memory, longer processing and more dead air for callers.
  • No redundant calls. Cache results in flow-level variables when data will be reused, and design actions to return everything needed in one call.
  • Prefer built-in functions. Where an expression does the job, use it. Genesys's example is using GetQueueEstimatedWaitTime() or FindQueueEstimatedWaitTime() instead of a data action, because built-ins avoid the overhead of an external call.
  • Move heavy processing out. If the backend cannot filter, a Genesys Cloud Function can receive the large data set, process and filter it in AWS Lambda, and return only the relevant result.

6.7 The loop anti-pattern

Genesys's named anti-pattern is a data action that returns 500 customers, followed by a loop that checks each one and exits when it finds a match. That pattern consumes hundreds or thousands of actions, creates significant dead air on calls and wastes memory on data nobody needed. The fix is to send the search criteria to the data action and get one record back.

The same thinking makes journeys faster in ways callers notice. An offer based on estimated wait, a balance and a last transaction, all pulled from one lookup near the top of the flow, beats three sequential calls, but only if you design the contract to return all three. We name actions after the journey moment they serve, such as GetAuthenticatedCustomerContext, rather than the endpoint they wrap, which is where Genesys's naming guidance leads too.

6.8 Rate limits, testing and monitoring

Data actions that call the Genesys Cloud API are subject to the platform's rate limits, published on the Developer Center limits page. Read the figures for your own organisation there, and handle rate limiting by waiting before retrying, as part 9 explains.

Test every action before a flow uses it. Genesys documents testing for draft and published custom actions, with credentials redacted in web services test output and a warning not to put sensitive data into test payloads. After go-live, the Data Actions Performance view in Analytics Workspace shows current and historical execution metrics, filterable by category, by the HTTP status codes the actions returned, and by date ranges of up to one month. Watch it after every release that changes an action.

07

Routing, rules, reference data and schedules

Architect's job ends where the queue begins, but flow design and queue design are one decision. This part covers how the flow hands work to queues, where rules and reference data should live, how schedules and emergencies are evaluated, and what the customer hears while waiting.

7.1 Plan flows and queues together

Genesys defines a queue as a pool of agents dedicated to a specific business need, and a skill as a tag assigned to a call to help route it more effectively, also applied to agents, so that a call tagged for Spanish reaches an agent tagged for Spanish.

Its planning guidance is blunt on the point most organisations get wrong: consolidating agents into larger answering groups is always more efficient than creating smaller queues in silos, and customers would rather wait for a skilled agent than reach a friendly voice who will transfer them. Every menu option that resolves into a separate small queue is a small tax on your service level. Our routing methods guide covers bullseye, conditional, preferred and predictive routing in detail.

7.2 Decision tables for rules

For rule-based logic, Genesys recommends the Call Decision Table action over building a rules engine from branches and conditions. The reasons it gives are central management of rules by administrators, better performance than custom branching, and easier maintenance and updates without flow changes. A twenty-condition eligibility rule in a flow is a maintenance liability; in a decision table it is a change an administrator can make and test.

Decision tables are created under Orchestration > Rule-Based Decisions. Genesys reads the rows in order, combines the conditions in each row with AND, and returns the result of the first row whose conditions are all met. Enum values are matched by key, not label. Order your rows from most specific to most general, as you would firewall rules.

  • An organisation can create up to 50 decision tables.
  • A table can have up to 30 attributes, of which at most 20 can be strings and 10 string lists.
  • If a flow has successfully run the Call Decision Table action five times, later invocations in that flow take the Failure path with the error type ActionInvocationLimitExceeded. Do not call a decision table inside a loop.
  • A newly published or rarely used table is prepared and optimised on first use, which can occasionally return ExecutionOutOfCapacityError. Map the failure outputs and handle it.
  • Success means the action completed without errors, not that the result is what you intended. Check the output before you route on it.
  • Genesys states that usage charges apply to rule-based decision executions. Confirm the commercial position with Genesys before you design high-volume use.

7.3 Data tables for reference data

Data tables hold configuration data inside Genesys Cloud, such as a mapping from account prefix to department, which the Data Table Lookup action reads by reference key. The action has Found, Not Found and Failure paths, with failure outputs for the error type and message. Handle all three: Not Found is a normal business outcome, and Failure is a platform event.

Genesys sets clear limits: 300 tables per organisation, 10,000 rows and 50 fields per table, with higher limits available on request. It is equally clear about content. Data tables are intended for configuration data and must not contain personal information or anything that could identify a living person. Customer records belong in the system of record, reached through a data action.

7.4 Schedules, holidays and emergencies

The Evaluate Schedule Group action routes on the open, closed, holiday and emergency schedules administrators maintain. Genesys documents the evaluation order: Emergency, then Holiday, then Closed, then Open, with Closed as the default when nothing else applies. You can evaluate at the current time or at a specified DateTime in UTC.

Operating schedule groups combine schedules and assign them to a time zone, which is how they absorb the clocks changing. Emergency groups let an administrator switch a location to emergency routing for unplanned or semi-planned events, such as a fire, a power cut or severe weather, without affecting other locations, and the Find Emergency Group action can locate one by name at runtime.

Build the closed, holiday and emergency paths first, not last. Out-of-hours calls ending in an empty queue is one of the commonest live defects, and it always comes from a path that was meant to be finished later.

7.5 In-queue flows and the waiting experience

In-queue call, email and message flows shape what happens while a customer waits for an agent. Which in-queue flow runs follows a documented order: an in-queue flow set on the Transfer to ACD action, with Override default in-queue handling enabled, takes precedence; then the flow selected for the queue on the Queues page; then the organisation's default in-queue flow.

For email and message interactions, Architect opens at most 30 in-queue flows per interaction. Genesys explains that the limit stops the interaction growing each time a Transfer to ACD action runs, which happens when a flow transfers to the queue it is already in. Avoid that pattern by design rather than relying on the limit.

The Play Estimated Wait Time action announces the wait in four modes: Approximate, Less Than, Padded and Precise. It uses Call.EstimatedWaitTime by default, and it rounds durations under one minute up to one minute. The Create Callback action places a callback request on a queue from an inbound, in-queue or outbound call. It captures the caller's number from ANI, so pair it with Collect Input when the caller wants to be called on another number. Callbacks are placed on behalf of the queue, and the action does not schedule a callback for a later time.

08

Participant data, flow outcomes and milestones

Participant data is the context that travels with a conversation and is visible to other flows, to scripts and to the public API. Flow outcomes and milestones are the reporting contract for self-service. They are often confused, and the difference matters for performance and for reporting.

8.1 How participant data behaves

Genesys documents different behaviour by flow type. In non-call flows, each Set Participant Data action makes a network request immediately, so several Set actions mean several requests and combining attributes improves performance.

In call flows, values are queued locally during execution and flushed to the cloud when the flow ends. Several Set actions do not create several requests during the call, but attributes set during the flow are not available through the public API until the flow completes. Combining Set actions still reduces the action count against the 10,000 limit. And if Get Participant Data does not find an attribute in the cloud, a call flow falls back to queued values not yet flushed.

8.2 The flush-on-completion trap

That behaviour is a real integration constraint. A CRM screen pop, a wallboard or any service that reads participant data through the API will not see a call-flow attribute until that flow ends. When the flow transfers to an agent, set everything the agent's tools need before the transfer, and pass context through the mechanism the integration actually reads, such as the script or screen pop configuration.

Get Participant Data is expensive in every flow type: each call makes a network request that retrieves all participant attributes and then filters to the ones you asked for. Genesys's rule is strict. Use it only when you know by design that the data may have been changed from outside the flow, for example by another system through the public API or by an earlier flow in the conversation. If the data came from the current flow, use flow variables.

8.3 What participant data is not for

Genesys's guidance on participant data
DoDo not
Pass essential context to other systemsUse it for logging or analytics
Use small key-value pairsStore large blobs of data
Use Get Participant Data only when data may have changed outside the flowUse Get Participant Data to read something set earlier in the same flow
Combine attributes into one Set Participant Data actionChain several Set Participant Data actions without need

8.4 Flow outcomes and milestones

For debugging, Genesys points to historical execution data (part 12). For journey reporting, it points to flow outcomes and milestones, which are designed for tracking customer journey events and do not consume participant data resources.

Initialize Flow Outcome starts the clock on an outcome; Set Flow Outcome records success or failure at a point in the flow; Add Flow Milestone records the steps in between. They are available in call, chat, email and message flows, but not in-queue call flows. An outcome that is initialised but never set is marked as a failure automatically when the interaction ends, which is exactly what you want for measuring abandonment.

By default an organisation can have up to 5,000 outcomes and 5,000 milestones, but analytics and performance views use only 20 milestones per outcome and 100 milestones per flow. The Flow Outcomes view in Analytics Workspace then reports success rates and duration.

09

Error handling and failure paths

A flow's quality shows in what happens when something goes wrong. Architect gives you two mechanisms and a documented retry discipline; a good flow uses both mechanisms on purpose and never leaves a caller to the default disconnect.

9.1 Two mechanisms

The first is default error handling, under Settings > Event Handling, for errors such as an invalid entry by a caller. For call, voicemail and in-queue call flows you choose the audio prompt to play; for all flow types you decide the flow's behaviour, with separate options documented for call and voicemail, digital, bot, in-queue and workitem flows.

The second is action-specific failure paths, available on the Call Data action, the Collect Input action and Transfer actions. Set the flow-level default first, then override it at the actions where a failure means something different.

9.2 Retry discipline

Genesys rejects unlimited or aggressive retries and prescribes a pattern: check whether the failure is worth retrying, add a short delay, retry at most once or twice, then fall back gracefully. For flows where failure outputs are available, it gives a table of error types worth adopting as a standard.

Whether to retry, by error type (Genesys guidance)
Error typeWhat to do
TimeoutMay be worth a single retry after a delay.
AuthenticationRetrying will not help. Fall back.
Rate limitingWait before retrying.
Invalid inputFix the input. Do not retry blindly.

9.3 Failure outputs in voice flows: check your organisation

The documentation points two ways on one detail, so check it in your own organisation. Genesys's Developer Center best practices page says that in call flows data actions have a failure path but no failure outputs giving the reason, so you cannot decide programmatically whether a retry is worthwhile. The Resource Center's Call Data action article now describes failure outputs that expose why the action failed, and the release note of 24 August 2026 says Architect voice flows now surface HTTP status codes and error reasons from data actions and secure data actions.

The newer pages suggest the capability is there. Confirm it in your own organisation before designing error-specific logic into a voice flow, and keep the safe default regardless: one or two retries with a delay, then a graceful fallback.

9.4 Pauses and dead air

Genesys documents a technique for a controlled pause in a call flow: a Play Audio action with blank audio of the length you need, such as 100 milliseconds, followed by a Flush Audio action. It gives a struggling backend a moment to recover before the retry.

Its warning on dead air applies to every retry and every data action on the voice path. Long silences frustrate callers; play informational audio during waits, keep total retry time reasonable, and have a clear exit if retries fail.

9.5 When the platform decides for you

Exceeding the action limit puts the flow into error handling. The default is to disconnect, but you can configure Transfer to ACD, Jump to Menu or Jump to Reusable Task instead. If you choose a menu or reusable task, Architect allows an extra 1,000 actions for that error path. Genesys stresses that this error budget is not a fresh allocation but a small allowance for handling the error gracefully, and exceeding it ends in a silent disconnect.

A silent disconnect, where the caller hears the line go dead with no prompt, is the worst failure available, and a design error alone can reach it. Always configure the error path, keep it short, and make sure it cannot loop back into the logic that exhausted the budget in the first place.

10

Limits, flow size and common modules

Budget these at design time. The limits below come from Genesys's documentation, checked on 15 November 2026. Genesys's reasons for them are protection rather than obstruction: preventing infinite loops, ensuring timely execution and protecting resources for every customer. Its design advice is that approaching a limit is a strong sign the flow needs optimising.

10.1 Execution limits

Architect execution limits and safeguards
LimitValueApplies to
Actions per invocation10,000Call, email, message and workflow flows
Error state actions1,000, used only after the action limit is exceeded; not a fresh allocationCall flows and workflows
Actions per invocation400, with 40 error state actionsWorkitem flows
Bot actions1,000 per turn and 10,000 per session, with at most 200 turnsBot and digital bot flows
Recorded action executionsOnly the first 4,500Call flows
Recorded value truncationJSON 1,000 characters, strings 253 characters, collections 20 itemsCall and bot flows
Automatic Base execution dataAbove 350 variablesCall flows
Data action execution timeoutConfigurable from 1 to 60 seconds, default 60Data actions integrations
Call Data action response2 MB maximumDigital, workflow, workitem and in-queue digital flows
Retry pauseUp to 90 secondsAsynchronous flows
In-queue flows per interaction30Email and message interactions
Decision table invocationsFive successful runs per flowCall Decision Table action

10.2 Flow size

Flow size is a separate budget from action count. The Flow Size view, under the flow's Insights and Optimizations, shows how much of the maximum the flow uses, accurate to 0.1%, with four documented states.

Flow size indicators and restrictions
IndicatorThresholdColourRestriction
LowBelow 30%BlueNone
Medium30%YellowNone
High70%RedNone
Full98%RedYou cannot publish, but you can save changes
  • At the maximum size you cannot save the flow, but you can still export it.
  • Common module flows have a lower size limit than other flow types.
  • Size can rise or fall as elements go in and out of error: an action in error does not count, so fixing one error that affects many actions can add a lot of size at once.
  • Genesys's stated purpose for the view is to let you decide in good time when to divide a flow into several flows.

10.3 Reducing flow size

Genesys lists practical ways to reduce size. Consolidate a run of Update Data actions, each with one statement, into one action with several statements. Avoid duplicating heavy actions: Call Data Action, Call Secure Data Action, Set Screen Pop and Create Callback can take a lot of space depending on configuration. And use variables to handle different values rather than creating several near-identical copies of an action. Both size and maintainability improve, because a change is made once.

10.4 Designing common modules

Common modules let you reuse logic across flows and flow types. Genesys's guidance treats them like functions, and the failure modes are the same. It rejects the Swiss Army knife module: one DoWork module with an operation input of add, update, delete or search, and parameters whose meaning changes with the operation. It prefers focused modules such as AddCustomer, UpdateCustomerEmail and DeleteCustomer, each with only the inputs it needs.

The reasons are clarity, efficiency, maintainability and performance, because input values are copied, not passed by reference, so unused parameters still consume resources. Define only the outputs callers will use, since output processing adds overhead. Do not mark a variable as both input and output for optimisation, because that increases the work on completion. If a module needs many related values, pass one JSON input, and first ask whether the module is trying to do too much.

10.5 How common module versions reach your flows

This behaviour catches teams out at release time. Architect snapshots the common module into each consuming flow. Publishing a new version of a module changes nothing in production until you republish the flows that call it, and each then picks up the latest version. To keep a flow on an older version, publish that flow before publishing the new module version. Dependency tracking shows which module versions each flow uses.

Other documented constraints: you cannot delete a common module that a published flow uses; you cannot call a common module from another common module; third-party TTS settings come from the consuming flow and cannot be set in the module; and a module made compatible with several flow types can only use the actions and data types those types share.

11

Secure flows for payment capture

A secure flow is Architect's mechanism for collecting sensitive information without recording it. Genesys describes it as a way to temporarily prevent system recording or agent access while a caller enters sensitive information, such as payment details, with the audio paths and data captured through the automated IVR masked. This part covers how secure flows behave; it is not a substitute for designing a payment journey with your qualified security assessor.

11.1 Two documented scenarios

Genesys documents two scenarios. In an agent-referred secure session, the agent sends the caller to a secure IVR segment, for example to take a card payment, and the caller returns to the agent afterwards. In an IVR-only secure session, there is no agent interaction or ACD routing. In both, sensitive information is not captured in recordings, not present in log files, and not visible or audible to agents or monitoring users.

11.2 Behaviours to design around

  • A flow takes on secure behaviour when it processes a secure action or when a variable's content is marked secure. A key icon marks anything secure, or consuming secure data, within a task.
  • Secure flows affect agent analytics: time in IVR, average time in IVR, agent handle time, average handle time and agent talk time. Warn the reporting team before you switch one on, or a change in the figures will be read as a change in performance.
  • If a bot session starts from a secure call flow, the bot inherits the secure characteristics of that flow, which limits logging and recording for compliance. Test the bot inside the secure context, not only on its own.
  • Secure flows report historical execution data at Base level only, regardless of organisation settings.
  • Only PCI-certified TTS engines can be used in secure call flows (part 5).
  • Genesys notes that when diagnostic recording options are enabled on a trunk for troubleshooting, that data is not encrypted. Keep diagnostics off for payment journeys unless you have agreed otherwise with your assessor.

11.3 Clearing card data after authorisation

Genesys's PCI data cleanup guidance uses a bot flow that takes a card payment by voice as its example. The caller speaks the card number, expiry date and security code, and each is stored in a secure variable before authorisation. Once the payment is authorised, the flow must clear both the security code variable and Session.LastCollectionUtterance, which holds the raw text of the caller's last response and may contain the spoken code.

The documented method is an Update Data action straight after the authorisation step, setting the secure security code variable and the last collected utterance to NOT_SET. It is a two-line change that is easy to miss in review, so put it on the checklist for every payment flow.

11.4 The platform's PCI DSS position

Genesys states that Genesys Cloud is Service Provider Level 1 compliant with PCI DSS version 4.0, validated by an external Qualified Security Assessor, and that all commercial and commercial satellite regions are certified against that standard. It also states that secure pause and secure call flows have been validated as Level 1 PCI DSS-compliant by an external assessor. PCI DSS compliance has to be enabled for the organisation through Genesys, and compliant organisations have DTMF logging and media capture by the Edge disabled.

Your own compliance is a separate question: Genesys publishes a customer responsibility matrix, and its attestation of compliance is available under a non-disclosure agreement. Confirm the current scope and settings with Genesys before you put them in a client document.

11.5 Secure pause for agent-handled calls

Secure flows are not the only control. Since the release of 2 March 2026, administrators can allow agents to use secure pause on all voice calls, including direct inbound and outbound calls and callbacks to numbers assigned to outbound campaigns; before that it was available only on ACD calls. Secure pause stops recording while the agent hears the details, so it does not take the agent out of scope in the way an IVR-only secure flow can. Choose between them with your assessor, journey by journey.

12

Testing and observability

Architect gives you four tools for checking a flow, plus the execution data that powers two of them. Use them in order: validate before publishing, debug the happy path, replay the failures, and read Flow Insights a week after release.

12.1 Validate

Architect checks the flow and shows a count of issues in red or yellow. Red errors prevent the flow from working and must be fixed before it can run; yellow items are suggestions or best practice recommendations that will not stop it working. Hovering over Validate lists each issue with an explanation, and selecting one takes you to where it is.

12.2 Debug

Debug lets you hear the flow from the caller's side by calling it from Genesys Cloud. It creates a separate version you can dial as a SIP address and shows extra information such as the actions taken and decision results. The flow must have no validation errors, debug is enabled from the Publish menu, and it works properly only for English-only flows (part 5).

Flow.IsTest tells the flow it is running in debug, which is how you stop real backend writes during a test call. Use it narrowly, around writes, and never branch production behaviour on it, or the thing you tested is not the thing that runs.

12.3 Replay mode

Since July 2024, replay mode lets authors replay and troubleshoot historical executions of flows of every type, stepping through what a real customer did and inspecting actions, errors and events. Open the flow that ran and go to Execution History; if the flow is in edit mode, first check in your work or revert to reach read-only. Choose an instance, then move back and forth through its execution items (actions, tasks and menus) on the timeline. You cannot edit the flow while in replay mode.

Replay is the right first tool for a complaint about a single call, because it is already in the organisation. Our own Innovation tools for single-conversation forensics and replaying one conversation through several flows go further when a journey crosses many flows.

12.4 Flow Insights

Flow Insights overlays how often actions, menu items, states and tasks actually run, to show customer behaviour and the parts of a flow that need improving, including containment, task completion and drop-off. Its documented constraints matter when you read it.

  • It works only in read-only mode.
  • It uses up to seven days of data, and data appears only after a flow ends, so interactions in progress show nothing.
  • For older versions, it uses the seven days before the version was unpublished.
  • It counts a component once per execution, however many times a loop ran it.
  • Frequency is measured against executions of the parent menu or task across all entry points, so a component can look dominant within its task and small within the flow.

12.5 Execution data levels

Historical execution data is what makes replay and Flow Insights possible, and it is opt-in. Storage is disabled by default. An administrator enables it under Admin > Account Settings > Organization Settings, in the Execution Data Storage section, with the Flow Instance Execution Data permissions, and flows must then be republished before data is captured. Individual flows can override the organisation's default level. The data counts towards the organisation's storage under the Genesys Cloud fair use policy, and executions that run longer than three days are not retained.

Execution data levels and Genesys's recommended use
LevelCapturesRecommended for
BaseThe high-level journey through actions, menus, errors and eventsProduction
NotesBase plus variable valuesDevelopment and testing
Verbose NotesNotes plus communication valuesDevelopment and detailed debugging
AllVerbose Notes plus action input and output valuesActive troubleshooting only, then remove

12.6 Execution data discipline

Genesys's reasoning for Base in production is that it is enough to see which actions ran and in what order, to find error paths and events, and to understand journeys through menus and decisions, while higher levels increase memory use during execution and use more storage. Its list of things not to do is short: do not leave flows at All in production, and do not use high execution data levels as a substitute for good flow design.

Remember the safeguards from part 10: only the first 4,500 actions of a call flow are recorded, values are truncated, and call flows with more than 350 variables drop to Base automatically. A complex flow cannot record everything, which is another reason to keep flows small.

13

Versions, promotion and governance

Flows are production code even though nobody types them. This part covers versions and recovery, dependencies, moving flows between organisations, validating flows after they are published, and the permissions and hygiene that keep an estate manageable.

13.1 Versions and the fastest recovery

Every flow version is one of three types: SAVE, CHECKIN or PUBLISH, as the Platform API's flow version object shows, along with the dates a version became and stopped being the published version. In Architect, the Available Versions dialog shows which version is published, the latest working copy and the latest check-in with its author. From a previous version you can unpublish the currently published version, export the configuration, or save a copy under a new name. Previous versions open read-only.

Unpublishing is the fastest recovery route on a bad day. It belongs in every release runbook, together with who is allowed to use it and what they must check afterwards.

13.2 Dependencies before deletions

Before renaming or deleting anything, find what uses it. Dependency search lists the flows that contain a given resource across more than 25 types, including skills, data actions, data tables, decision tables, prompts, queues, schedules, scripts and secure call flows, with version information. It covers checked-in and published flows only, not working or unsaved ones. Genesys also documents searching for flows that use a deleted resource, and rebuilding the dependency database when the index is stale.

Deleting flows is deliberately restricted. You cannot delete a flow that another user has locked, that is associated with an IVR configuration, or that another resource, such as another flow or a script, consumes.

13.3 YAML export and Archy

Architect can export a flow as YAML, optionally with tracking IDs. You can edit the file in a text editor and import it with Archy into the same organisation or another, rather than recreating a flow by hand and remapping queues, task logic and menus. Moving a flow between test and production by hand loses its mappings to queues, data actions and more; with Archy you can update those mappings with find and replace, and its substitutions file supplies organisation-specific values from outside the flow.

Archy is a command-line YAML processor for Linux, macOS and Windows, built on the Genesys Cloud Platform SDK and Architect Scripting SDK. It can check flows in and out, publish them and update them, and Genesys states it is intended for use in automated environments such as CI/CD pipelines.

Know one caveat before you promise a pipeline: sequence builders are not supported in YAML export. The export renders them as equivalent expressions, which Genesys says work as expected, but the round trip does not preserve the form the author built.

13.4 CX as Code for the configuration around flows

Flows depend on queues, skills, schedules, data actions, data tables and more. CX as Code is Genesys's Terraform provider for managing that configuration declaratively across organisations, with an export resource that can turn existing configuration into Terraform files. Used alongside Archy, it lets a team promote a flow and everything it depends on from development to test to production in a repeatable way.

13.5 Validating flows after they are published

A flow can be valid when published and invalid weeks later because something it depends on has changed. Since the release of 26 October 2026, administrators can use the Architect flow validator, through the Archy command line or Archy CX as Code, to find published flows that have become invalid because of platform or dependency changes, before they fail at runtime. Run it on a schedule and after every configuration release, not after an incident.

13.6 Permissions

Architect bases permissions on flow design tasks or job functions, assigned by an administrator, and changes can take a few minutes to take effect. Access to the interface is Architect > UI > View; flow work uses Architect > Flow > Add, Edit and Delete, where Edit covers locking, checking in, saving, exporting and discarding changes. Grant authors the minimum they need, and keep publish rights in production with the people accountable for releases.

13.7 Naming and hygiene

Genesys treats naming as practice, not style: give actions meaningful names instead of the defaults, because, as with code, descriptive names make flows easier to understand, debug and maintain. Be descriptive (GetCustomerAccount rather than Call Data Action), concise and consistent across flows. Flow names must be unique within a flow type.

  • Remove unused variables and review variable use regularly during development.
  • Watch flow size in Insights and Optimizations at every release.
  • Search for flows that use a deleted resource after any decommissioning.
  • Keep the voice register (part 5) and the outcome definitions (part 8) current.
  • Record the flow version in participant data or logs, so every incident can be traced to a version.

13.8 A release discipline that works

Genesys does not prescribe a promotion model, so this part is ours. Separate development, test and production organisations, with flows promoted by Archy and configuration by CX as Code, give you repeatable releases and a version history outside the platform. Each flow change is reviewed by a second author against a short checklist before it is published, and every release has a named rollback route.

14

A worked example and the failures we see most

This part puts the handbook together. The worked example is illustrative, built from the documented behaviours above, not taken from any client's flow. The failure table is our own pattern list from reviewing and rebuilding flows, with each entry resting on the documented behaviour named beside it.

14.1 The journey: balance enquiry and transfer

An inbound call flow on a single number lets customers hear their account balance or speak to an agent. The design goals are to ask for as little as possible, keep every wait short, report containment accurately and never leave a caller in silence.

Entry. The flow checks the schedule group first. Emergency, holiday and closed paths are built and tested before the open path, each with its own message and destination.

14.2 Identify and authenticate

Identify. A targeted web services data action, GetCallerIdentity, takes the caller's number and returns a customer ID, tier and a flag for whether the customer is already authenticated elsewhere. Nothing else. The result goes into one JSON variable, customerContext. The flow timeout is three seconds, and the Timeout and Failure paths both lead to manual identification rather than an agent, because the caller can still self-serve.

Ask only if necessary. A Decision checks customerContext for a customer ID. If the number matched, the flow goes straight to verification. If not, Collect Input asks for the account number: exact length, individual-digit verification, a sensible no-entry timeout, and its own failure path. Asking for an account number when the caller's number already matched is the quickest way to lose them.

Authenticate. Two focused common modules, VerifyVoicePin and SendSmsPasscode, rather than one Authenticate module with a method input. One retry, with a short blank-audio pause before the second attempt, then a graceful transfer to an agent. An authentication failure is exactly the case Genesys says retrying will not fix.

14.3 Decide, hand off and fail safely

Decide the route. A Call Decision Table, RouteByTierAndReason, chooses the queue and priority, so business owners can change routing rules without a flow change. It is called once, never in a loop, and its failure outputs are mapped.

Hand off. One Set Participant Data action carries the customer ID, tier, reason, authentication result and self-service result, set before the transfer so the agent's tools can see it. Set Flow Outcome records BalanceSelfService as success or failure, with milestones at identification, authentication and balance played. Transfer to ACD has its own failure path to an overflow queue.

Fail safely. Flow-level event handling plays a short apology and transfers to an agent. Action-level failure paths cover the data action, Collect Input and the transfer. The action-limit error path transfers to an agent in a handful of actions. Nothing is left to the default disconnect.

After publishing. Validate with zero issues, debug the happy path in English, run real test calls for the other languages, set execution data to Notes in test and Base in production, and read Flow Insights and the Flow Outcomes view a week after release. Then replay the transfers nobody expected.

14.4 Failure modes and their fixes

Common Architect failure modes, causes and fixes
SymptomLikely causeFix
Caller hears silence, then the line dropsAction limit exceeded and the error path exhausted its 1,000-action allowance: a silent disconnectConfigure a short error path; reduce actions; split the flow (parts 9 and 10)
A branch never completesNo closing action on the branchEvery task or state needs a closing action (part 3)
A flow that worked suddenly failsA dependency changed after publishing and the flow became invalidRun the flow validator through Archy on a schedule (part 13)
Long dead air before a promptA large data action payload, or several sequential data actionsTargeted actions, smaller responses, one combined call, a processing prompt (part 6)
Backend overwhelmed during an outageAggressive retriesOne or two retries with a delay, then a graceful fallback (part 9)
Agent's screen pop is emptyCall-flow participant data is flushed only when the flow endsSet data before the transfer; use what the integration reads (part 8)
Rules stop working after a few calls in one flowThe Call Decision Table action was run more than five times in one flowCall the table once; never inside a loop (part 7)
Two reports disagree on time in IVRSecure flows change IVR and handle-time metricsTell reporting before enabling; document it (part 11)
Account numbers lose leading zerosImplicit casting between string and numberKeep identifiers as strings; cast deliberately (part 4)
Press zero does nothing during account entryMenu DTMF and speech recognition are disabled during Collect InputHandle the escape inside the action (part 4)
A common module fix has no effectModules are snapshotted into consuming flowsRepublish every consuming flow (part 10)
A language plays the wrong voice or errorsTTS is set per flow and language; None raises a validation error; defaults need a republishSet engines in Supported Languages and republish (part 5)
The flow cannot be publishedFlow size reached 98%Split the flow; reduce size (part 10)
Replay shows nothingExecution data storage is off by default, or flows were not republishedEnable storage, republish, and remember the seven-day Flow Insights window (part 12)

Questions

Common questions

How many actions can a Genesys Cloud Architect flow run?

Call, email, message and workflow flows can run 10,000 actions per invocation; workitem flows 400; bot flows 1,000 per turn and 10,000 per session. Exceeding the limit triggers error handling. If the error path jumps to a menu or task, Architect allows an extra 1,000 actions for it; exceeding that ends in a silent disconnect, so keep the error path short.

What happens when an Architect flow gets too big?

The Flow Size view shows how much of the maximum a flow uses. At 98% you can save but not publish, and at the maximum you can only export. Common modules have a lower size limit. Genesys recommends using the view to decide when to split a flow; we start that conversation at 30%.

Why does my common module change not appear in live calls?

Architect snapshots a common module into every flow that calls it. Publishing a new module version changes nothing until you republish the consuming flows, which then pick up the latest version. Use dependency search to list them, and republish and test each one as part of the release.

Should I use a decision table or a data table in Architect?

Use a decision table for rules that return a result from several conditions, such as routing by tier and reason; Genesys reads its rows in order and returns the first full match. Use a data table for simple lookups by key. Data tables must not hold personal data, and a flow can successfully run the Call Decision Table action only five times.

Why can't the agent see data the IVR set?

In call flows, Set Participant Data values are queued and flushed to the cloud only when the flow ends, so anything reading them through the public API, such as a screen pop or wallboard, cannot see them earlier. Set everything the agent needs before the transfer, combined into one action, and pass context through the mechanism the integration reads.

Which execution data level should production flows use?

Genesys recommends Base in production, Notes or Verbose Notes in development and testing, and All only during active troubleshooting. Execution data storage is off by default; once enabled, flows must be republished before data is captured. Secure flows record at Base only, and call flows record only their first 4,500 actions.

Sources

  1. About Architect – Genesys Cloud Resource Centerhelp.genesys.cloud
  2. In-queue flow precedence – Genesys Cloud Resource Centerhelp.genesys.cloud
  3. About the Genesys Cloud Function data actions integration – Genesys Cloud Resource Centerhelp.genesys.cloud
  4. About variables and expressions – Genesys Cloud Resource Centerhelp.genesys.cloud
  5. Add Flow Milestone action – Genesys Cloud Resource Centerhelp.genesys.cloud
  6. Call Common Module action – Genesys Cloud Resource Centerhelp.genesys.cloud
  7. Call Decision Table action – Genesys Cloud Resource Centerhelp.genesys.cloud
  8. Create and publish decision tables – Genesys Cloud Resource Centerhelp.genesys.cloud
  9. Create Callback action – Genesys Cloud Resource Centerhelp.genesys.cloud
  10. Data Actions Performance Summary view – Genesys Cloud Resource Centerhelp.genesys.cloud
  11. Data Table Lookup action – Genesys Cloud Resource Centerhelp.genesys.cloud
  12. Emergencies – Genesys Cloud Resource Centerhelp.genesys.cloud
  13. Evaluate Schedule Group action – Genesys Cloud Resource Centerhelp.genesys.cloud
  14. Flow Outcomes Summary view – Genesys Cloud Resource Centerhelp.genesys.cloud
  15. Historical execution data overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  16. Initialize Flow Outcome action – Genesys Cloud Resource Centerhelp.genesys.cloud
  17. Loop action – Genesys Cloud Resource Centerhelp.genesys.cloud
  18. Manage execution data at the flow level – Genesys Cloud Resource Centerhelp.genesys.cloud
  19. Operating schedule groups – Genesys Cloud Resource Centerhelp.genesys.cloud
  20. PCI DSS customer responsibility matrix – Genesys Cloud Resource Centerhelp.genesys.cloud
  21. Phone number searches with the data action integration – Genesys Cloud Resource Centerhelp.genesys.cloud
  22. Play Estimated Wait Time action – Genesys Cloud Resource Centerhelp.genesys.cloud
  23. Search for flows by dependency – Genesys Cloud Resource Centerhelp.genesys.cloud
  24. Set Flow Outcome action – Genesys Cloud Resource Centerhelp.genesys.cloud
  25. Test data actions for integrations – Genesys Cloud Resource Centerhelp.genesys.cloud
  26. Understand execution of decision tables – Genesys Cloud Resource Centerhelp.genesys.cloud
  27. Work with common module flows – Genesys Cloud Resource Centerhelp.genesys.cloud
  28. Work with data tables – Genesys Cloud Resource Centerhelp.genesys.cloud
  29. Work with in-queue flows – Genesys Cloud Resource Centerhelp.genesys.cloud
  30. Add contracts to custom actions for integrations – Genesys Cloud Resource Centerhelp.genesys.cloud
  31. Add text to speech to a user prompt – Genesys Cloud Resource Centerhelp.genesys.cloud
  32. Architect built-in variables – Genesys Cloud Resource Centerhelp.genesys.cloud
  33. Architect flow size – Genesys Cloud Resource Centerhelp.genesys.cloud
  34. Architect permissions overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  35. Set the timeout behavior – Genesys Cloud Resource Centerhelp.genesys.cloud
  36. Choose the organization's default TTS engine – Genesys Cloud Resource Centerhelp.genesys.cloud
  37. Collect Input action – Genesys Cloud Resource Centerhelp.genesys.cloud
  38. Create a flow – Genesys Cloud Resource Centerhelp.genesys.cloud
  39. Define Architect flows using YAML – Genesys Cloud Resource Centerhelp.genesys.cloud
  40. Expressions tips and best practices – Genesys Cloud Resource Centerhelp.genesys.cloud
  41. Failure paths in Architect – Genesys Cloud Resource Centerhelp.genesys.cloud
  42. Validate a flow – Genesys Cloud Resource Centerhelp.genesys.cloud
  43. Flow execution history – Genesys Cloud Resource Centerhelp.genesys.cloud
  44. Language support and TTS – Genesys Cloud Resource Centerhelp.genesys.cloud
  45. Manage a variable – Genesys Cloud Resource Centerhelp.genesys.cloud
  46. Navigate the Architect home page – Genesys Cloud Resource Centerhelp.genesys.cloud
  47. PCI DSS compliance – Genesys Cloud Resource Centerhelp.genesys.cloud
  48. Plan interaction flow and queue design – Genesys Cloud Resource Centerhelp.genesys.cloud
  49. Release notes for the web services data actions integration – Genesys Cloud Resource Centerhelp.genesys.cloud
  50. Secure flow scenarios – Genesys Cloud Resource Centerhelp.genesys.cloud
  51. Secure flows overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  52. Select a TTS engine and voice for a flow – Genesys Cloud Resource Centerhelp.genesys.cloud
  53. Set default event handling behavior – Genesys Cloud Resource Centerhelp.genesys.cloud
  54. Set up user input for a voice survey flow – Genesys Cloud Resource Centerhelp.genesys.cloud
  55. Task and state editor actions – Genesys Cloud Resource Centerhelp.genesys.cloud
  56. Task and state editor overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  57. Test a flow – Genesys Cloud Resource Centerhelp.genesys.cloud
  58. Text-to-speech (TTS) engines overview – Genesys Cloud Resource Centerhelp.genesys.cloud
  59. Use data actions in Architect for integrations – Genesys Cloud Resource Centerhelp.genesys.cloud
  60. Use Flow Insights to view the frequency of executed flow components – Genesys Cloud Resource Centerhelp.genesys.cloud
  61. Implicit casting in expressions – Genesys Cloud Resource Centerhelp.genesys.cloud
  62. Use replay mode to troubleshoot an Architect flow – Genesys Cloud Resource Centerhelp.genesys.cloud
  63. Use shortcuts from the More menu in Architect – Genesys Cloud Resource Centerhelp.genesys.cloud
  64. View previous versions of a flow – Genesys Cloud Resource Centerhelp.genesys.cloud
  65. Work with expressions – Genesys Cloud Resource Centerhelp.genesys.cloud
  66. Work with secure call and bot flows – Genesys Cloud Resource Centerhelp.genesys.cloud
  67. How many actions can I run in a flow? – Genesys Cloud Resource Centerhelp.genesys.cloud
  68. August 02, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  69. August 24, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  70. December 2, 2024 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  71. July 22, 2024 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  72. March 2, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  73. October 26, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
  74. Call Data action – Genesys Cloud Resource Centerhelp.genesys.cloud
  75. Call Bot Flow action – Genesys Cloud Resource Centerhelp.genesys.cloud
  76. Architect Flow Best Practices – Genesys Cloud Developer Centerdeveloper.genesys.cloud
  77. Welcome to Archy! – Genesys Cloud Developer Centerdeveloper.genesys.cloud
  78. CX as Code – Genesys Cloud Developer Centerdeveloper.genesys.cloud
  79. Limits – Genesys Cloud Developer Centerdeveloper.genesys.cloud
  80. API Explorer: get a flow version – Genesys Cloud Developer Centerdeveloper.genesys.cloud
  81. Genesys Cloud CX summarised plan comparison – Genesyslibrary.genesys.com

Last reviewed

We work by introduction

Clients, partners and people introduced to us can reach the right specialist directly.

Who to contact