describe_flow_execution_records returns empty flowExecutions on first run

[kuratami711]

Summary

When calling describe_flow_execution_records immediately after triggering a flow for the first time, the flowExecutions list is sometimes empty, even though the flow has been successfully started.

Steps to Reproduce

1. Create a new AppFlow flow.
2. Start the flow using start_flow.
3. Immediately call describe_flow_execution_records with maxResults=1.
4. Observe that flowExecutions is an empty list.

Expected Behavior

The most recent flow execution record should be returned, even on the first run.

Actual Behavior

The flowExecutions list is empty for a short period after the first execution. This requires polling with retries to eventually retrieve the execution record.

Questions

• Is this behavior expected (i.e., due to eventual consistency)?
• Or is this a bug in the AppFlow API or SDK?

Environment

• SDK: boto3
• AppFlow API: describe_flow_execution_records
• Region: ap-northeast-1
• Python version: 3.12

Thank you for your support.

Note: I am not fluent in English, so please forgive any awkward expressions.

[kuratami711]

I’ve opened a formal issue for this topic here: [link to the issue]
Closing this discussion to avoid duplication.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.