How long does this process take?

📘
Webhooks v3 bulk export of failed events is a new Identity Cloud feature currently in limited availability. Because the feature isn't in general release, that means that both the product, and this documentation, are subject to change at any time.

In general. It takes very little time to complete a job or to download a file. Although times will vary, you can expect a job consisting of 10,000 or fewer events to complete in less than 10 seconds. Even a job containing as many as one mill events will typically complete in less than one minute.

One thing you need to keep in mind, however, is that there can only be one job running at a given time in a given Identity Cloud region. For example, suppose you start a job in the US region and then immediately try to start a second job in that region. Most likely that second job is going to fail with the following error:

{
    "status": 409,
    "title": "Conflict",
    "details": "Too many active exports"
}

That’s because the first job hasn’t finished yet and, as noted, each region can only run one job at a time. And that limitation doesn’t only apply to your organization. For example, suppose organization A starts a job. Organization B, which happens to be in the same region, can’t start a job until Organization A’s job has finished. Because jobs are rarely used (again, these jobs are designed to help you recover from catastrophic Webhook failures) collisions like this will be rare. If they do happen, however, organization B can just wait a minute or two and then try again.

Downloading the files is also remarkably fast. Again, outside factors (such as network congestion) can cause your download times to vary slightly. However, Identity Cloud tests resulted in the following download times:

Number of events	Download time
100,000	11 seconds
1 million	49 seconds
10 million	6 minutes and 55 seconds

You can use those numbers to roughly estimate how long it will take to download one of your files.

See also