The Cognito User Sync job has been changed so that it runs immediately in in amended as below
No change made to Dev, Test, and Prod environments
...
and it runs immediately.
For any additional environments, a 10-minute delay has been introduced before the job completes.
What caused the issue?
AWS Cognito in AWS has a limited amount limit on the number of API calls that it can handle over within a set period of specific time frame. If the When lower environments all run at the same time as run concurrently with Prod and each other, it can cause this limit can be exceeded, causing the job to fail as the limit can be exceeded. The jobs often run at the same time as each refresh sets the lower environment to have . This issue arises because lower environments inherit the same job schedule as Production during refreshes, leading to simultaneous job execution.
Why did we delay the start of the job?As a fix, we have delayed any environment implement the delay?
To address this, we’ve added a 10-minute delay for environments beyond Dev, Test, and Prod to 10 minutes after the job is started. This will make sure that limit is not exceeded and that the job does not fail due to exceeding the API Call limit. How does this affect . This staggered timing ensures the API call limit isn’t exceeded, preventing job failures.
What does this mean for you?
If you have non-Prod environments beyond Dev and Test, you may notice a 10-minute delay in the Cognito User Sync job will have a 10 minute delay. This can give the appearance that the . This delay is intentional and designed to improve system stability, even if it appears the job is taking longer when it is actually by designto complete.