What is the step you perform after listening to the updated event in the Stripe report API workflow?

What is the step you perform after listening to the updated event in the Stripe report API workflow?

• A. Download your report via the link
• B. Create a reportrun for that day's data via the API
• C. Stripe sends a report_run.succeeded webhook
• D. Listen to the event

Answer: (B)

In Stripe’s Reports workflow, generating reports is an asynchronous process that you drive with API calls and monitor via webhooks. When you receive an update about a report_run, the practical next step is to kick off the next day's data by creating a new report_run for that day through the API. This starts a fresh run so you can keep the daily data flowing. After you initiate the new run, Stripe will emit updates as it processes, and once it succeeds you can download the report via the provided URL. The other steps—downloading the report via a link, or waiting for a report_run.succeeded webhook, or simply listening for events—are part of the flow, but the action that advances the automation after an update is to create a new report_run for that day's data.

In Stripe’s Reports workflow, generating reports is an asynchronous process that you drive with API calls and monitor via webhooks. When you receive an update about a report_run, the practical next step is to kick off the next day's data by creating a new report_run for that day through the API. This starts a fresh run so you can keep the daily data flowing. After you initiate the new run, Stripe will emit updates as it processes, and once it succeeds you can download the report via the provided URL.

The other steps—downloading the report via a link, or waiting for a report_run.succeeded webhook, or simply listening for events—are part of the flow, but the action that advances the automation after an update is to create a new report_run for that day's data.