Source note · Genesys Cloud Architect flows
For outbound digital interactions the in-queue flow does not launch, even if set as default, until an inbound response arrives.
Checked 2026-09-25
The in-queue flow launches only after an inbound response arrives.
- Vendor
- Genesys
- Product
- Genesys Cloud Architect
- Subsystem
- in-queue flows
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- In-queue flows overview — Genesys · tier 2 current vendor documentation · In-queue flows overview; outbound interactions note
Cite this note
APA
WarmTransfer. (2026, September 25). Genesys Cloud Architect flows: source note genesys-architect-flows-inqueue-outbound-no-launch. WarmTransfer. https://warmtransfer.net/knowledge/claims/genesys-architect-flows-inqueue-outbound-no-launch
BibTeX
@misc{warmtransfer-claim-genesys-architect-flows-inqueue-outbound-no-launch,
title = {Genesys Cloud Architect flows: source note genesys-architect-flows-inqueue-outbound-no-launch},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/genesys-architect-flows-inqueue-outbound-no-launch},
note = {Source note genesys-architect-flows-inqueue-outbound-no-launch, checked 2026-09-25}
}