Source note · Omnichannel routing and channel capacity
If an Amazon Connect contact's workload type has no matching entry in the agent's routing profile, the contact remains queued indefinitely.
Checked 2026-09-30
- Vendor
- Amazon Web Services
- Product
- Amazon Connect
- Subsystem
- routing profiles
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Channels and concurrency for routing contacts in Connect Customer — Amazon Web Services · tier 2 current vendor documentation · Workload-type concurrency, 'Important' box
Cite this note
APA
WarmTransfer. (2026, September 30). Omnichannel routing and channel capacity: source note omnichannel-routing-concepts-aws-workload-unmatched. WarmTransfer. https://warmtransfer.net/knowledge/claims/omnichannel-routing-concepts-aws-workload-unmatched
BibTeX
@misc{warmtransfer-claim-omnichannel-routing-concepts-aws-workload-unmatched,
title = {Omnichannel routing and channel capacity: source note omnichannel-routing-concepts-aws-workload-unmatched},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/omnichannel-routing-concepts-aws-workload-unmatched},
note = {Source note omnichannel-routing-concepts-aws-workload-unmatched, checked 2026-09-30}
}