Cognito User Sync Job in Non-Prods

The Cognito User Sync job has been 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 has a limit on the number of API calls it can handle within a specific time frame. When lower environments run concurrently with Prod and each other, this limit can be exceeded, causing the job to fail. This issue arises because lower environments inherit the same job schedule as Production during refreshes, leading to simultaneous job execution.

Why implement the delay?

To address this, we’ve added a 10-minute delay for environments beyond Dev, Test, and Prod. 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. This delay is intentional and designed to improve system stability, even if it appears the job is taking longer to complete.