Flow data in the Connect Customer data lake
The following tables contain flow data.
Contact flow events
Table name:
contact_flow_events
Description: Records contact flow execution events, tracking flow traversal including start and end timestamps, flow outcomes, and transitions between flows and queues.
Primary key:
event_id, instance_id
Partition key:
start_timestamp (daily)
Join keys:
instance_id— Joins to all tablescontact_id— Joins to Contact Record, Contact Statistic Record, Contact Lens, Contact Evaluation Recordflow_resource_id— Joins to flow configuration datanext_queue_resource_id— Joins to Contact Record (asqueue_id), Agent Queue Statistic Record (asqueue_id)
| Column | Type | Nullable | Description |
|---|---|---|---|
| instance_id | string | No | The identifier of the Connect Customer instance. You can find the instance ID in the Amazon Resource Name (ARN) of the instance. |
| event_id | string | No | The ID of the contact as it interacts with the flow. |
| aws_account_id | string | No | The ID of the AWS account that owns the contact. |
| instance_arn | string | No | The ARN of the Connect Customer instance. |
| contact_id | string | No | The ID of the contact in the contact record. |
| flow_resource_id | string | No | Flow Id |
| module_resource_id | string | No | Module Id |
| resource_version | string | No | Version of the contact flow used. |
| resource_type | string | No | Can be flow or module. |
| channel | string | No | The method used to contact your contact center: VOICE, CHAT, TASK, EMAIL. |
| start_timestamp | Timestamp | No | Date and time of the start event in unix epoch, UTC |
| end_timestamp | Timestamp | No | Date and time of the end event in unix epoch, UTC. |
| next_flow_resource_id | string | No | Next contact flow resourceId. |
| next_queue_resource_id | string | No | Next queue resourceId. |
| next_resource_type | string | No | It can be flow or queue. |
| flow_language_version | string | No | Flow language version. |
| flow_outcome | string | No | This will contain the system defined and custom outcomes. |
| sub_type | string | No | This field can be used to show channel subtype. For example, connect:Guide or connect:SMS or connect:Email. |
| flow_type | string | No | Connect Customer includes a set of nine flow types. For more information, see Choose a flow type. |
| initiation_method | string | No | Every contact in your Connect Customer contact center is initiated by one of the following methods: Inbound, Outbound, Transfer, Callback, API, Queue Transfer, Disconnect. |
| resource_published_timestamp | Timestamp | No | "Creation" or "revision" date of the flow itself. |
| data_lake_last_processed_timestamp | Timestamp | No | The Timestamp, which shows the last time the data lake processed the record. This can include transformation and backfill. This field cannot reliably be used to determine data freshness. |
Connect test case execution results
Table name:
connect_test_case_execution_results
Description: Stores test case execution results including status, outcomes, failure reasons, and associated contacts for Connect test automation.
Primary key:
connect_test_case_resource_arn, connect_test_case_execution_start_timestamp, connect_test_case_execution_id
Partition key:
connect_test_case_execution_start_timestamp (daily)
Join keys:
instance_id— Joins to all tablesconnect_test_case_associated_initial_contact_id— Joins to Contact Record (ascontact_id)connect_test_case_initiating_flow_id— Joins to Contact Flow Events (asflow_resource_id)
| Column | Type | Nullable | Description |
|---|---|---|---|
| instance_id | string | Yes | The identifier of the Amazon Connect instance |
| instance_arn | string | Yes | The ARN of the Amazon Connect instance. |
| aws_account_id | string | Yes | The ID of the AWS account that owns the contact. |
| connect_test_case_resource_arn | string | No | Primary Key - The ARN of the Test Case. |
| connect_test_case_resource_name | string | Yes | The name of the Test Case. |
| connect_test_case_execution_start_timestamp | timestamp | No | Primary Key - The start time of simulated execution. |
| connect_test_case_execution_end_timestamp | timestamp | Yes | The end time of simulated execution. |
| connect_test_case_status | string | Yes | Current state of Test. Values: Scheduled, InProgress, Completed, Aborted, Failed |
| connect_test_case_result | string | Yes | The final result of Test execution. Values: Passed, Failed, Skipped, Aborted |
| connect_test_case_execution_id | string | No | Primary Key - The unique identifier for Test execution. |
| connect_test_case_failure_reasons | array(string) | Yes | The reasons for failed Test. |
| connect_test_case_type | string | Yes | The type of Test executed. Values: ExperienceTest, FlowTest, BotTest |
| connect_test_case_execution_method | string | Yes | The method of starting Test execution. Values: Manual, API, Scheduled, ContactRuleTriggered, FlowPublishTriggered |
| connect_test_case_execution_channel | string | Yes | The channel of simulated interaction. Values: Chat, Voice, Campaign, Task, Email |
| connect_test_case_execution_channel_subtype | string | Yes | The channel subtype of simulated interaction. Values: SMS, WhatsApp |
| connect_test_case_associated_initial_contact_id | string | Yes | Initial contact ID to start Test. |
| connect_test_case_associated_contact_ids | array(string) | Yes | List of contact IDs created as part of Test. |
| connect_test_case_initiating_flow_id | string | Yes | First resource ID Test Execution started with. |
| record_creation_timestamp | timestamp | Yes | The time of record creation |
| data_lake_last_processed_timestamp | Timestamp | Yes | The timestamp, which shows the last time the record was touched by the data lake. This can include transformation and backfill. This field cannot reliably be used to determine data freshness. |
