Claim record · Amazon Connect contact flows and routing profiles
If a contact's workload type does not match any workload-type row in the routing profile, the contact stays in queue indefinitely.
fact · verified 2026-09-07
Missing entries cause contacts to queue indefinitely.
- Vendor
- Amazon Web Services
- Product
- Amazon Connect Customer
- Subsystem
- routing-profiles
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-07
- Status
- fact
- Confidence
- 0.90
- Verified
- 2026-09-07
Sources
- Create a routing profile in Connect Customer to link queues to agents — Amazon Web Services · tier 2 current vendor documentation · Step 4 Rules and validations final bullet, repeated in Tips for setting up channels and concurrency
Cite this claim
APA
WarmTransfer. (2026, September 7). Amazon Connect contact flows and routing profiles: claim amazon-connect-flows-workload-mismatch-stuck. WarmTransfer. https://warmtransfer.net/knowledge/claims/amazon-connect-flows-workload-mismatch-stuck
BibTeX
@misc{warmtransfer-claim-amazon-connect-flows-workload-mismatch-stuck,
title = {Amazon Connect contact flows and routing profiles: claim amazon-connect-flows-workload-mismatch-stuck},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/amazon-connect-flows-workload-mismatch-stuck},
note = {Claim amazon-connect-flows-workload-mismatch-stuck, verified 2026-09-07}
}