CloudWatch tells you the flow ran

About five minutes of reading

Without flow logs you are guessing which block took the error branch.

Set logging behavior writes a record per block to CloudWatch Logs. Search for Results like Error, and filter the Lambda block type InvokeExternalResource. The ContactId is the join to Lambda's own log if the function printed it.

The email quota note recommends an alarm at 80 percent of concurrent emails. Use the same habit for calls, chats, and tasks.

• Logging can be turned off in the flow. Check that before you blame the log group.
• A missing error in Lambda's log with an error in the flow log means Connect rejected the response before or without a completed invoke.
• Metrics such as ConcurrentEmails belong in an alarm, not in a monthly slide.
• Flow logs are not a recording and not a CTR.

Number on this page: Alarm at 80%. Of the quota, as an operating habit

Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.

Picture from this room.

1. Turn on. Set logging behavior.
2. Fail once. Capture ContactId.
3. Query. Results LIKE Error.
4. Change. One block, then retest.

What usually goes wrong: Editing the flow again before you have read the log of the failed ContactId.

Troubleshoot contact flow errors in Amazon Connect | AWS re:Post community. last checked 2026-10

The prose is a study paraphrase. The link is the source of the facts.

Glossary

• Contact One interaction: a call, chat, task, or email. A transfer usually creates another contact linked by PreviousContactId and NextContactId.
• Connect Customer The name used from 28 Apr 2026 for the contact center product previously called Amazon Connect.
• CloudWatch Metrics and flow logs. Alarm at 80 percent of a quota, which is the operations guidance in the email quota note.
• Kinesis Data Streams The durable stream for CTRs and agent events when more than one consumer must read them.

Mind map

Open the Foundations mind map

Sister technologies

A flow fails in IAM, a Region, a log group, or a network rule long before it fails as a 'Connect bug'.

Config and troubleshooting

Editing the flow again before you have read the log of the failed ContactId.

IAM, Lambda, S3, Kinesis, and CloudWatch are not inside the instance. This stack creates the instance and turns on flow logs and Contact Lens.

CfnInstance AWS::Connect::Instance

AWSTemplateFormatVersion: "2010-09-09"
Description: Connect instance with flow logs and Contact Lens
Resources:
  CampusInstance:
    Type: AWS::Connect::Instance
    Properties:
      IdentityManagementType: SAML
      InstanceAlias: campus-demo
      Attributes:
        InboundCalls: true
        OutboundCalls: true
        ContactflowLogs: true
        ContactLens: true

Integration map

Join records on ContactId. The integration map room lists the seams.

Cross-platform bridges

A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.

Open the mapping room

Future hooks

Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.