Outbound Campaign API 429s during JMeter load test in ap-southeast-1

General Discussion
1

Can anyone clarify the validation logic for outbound campaign creation via Terraform?
Provider version 1.65.0. Deploying a campaign with genesyscloud_outbound_campaign.
Apply fails with 429 Too Many Requests. Error: “Rate limit exceeded for account.”

Is there a specific wait strategy or retry logic needed in the HCL provider for outbound resources?

2
  1. Implement exponential backoff in your HCL retry block.
  2. Set min_delay_seconds = 1 and max_delay_seconds = 60.
  3. Ensure retry_max_attempts = 5.

The outbound API enforces strict rate limits in ap-southeast-1. The default provider retry is too aggressive. This configuration aligns with AppFoundry best practices for handling 429s during bulk provisioning.

3

It depends, but generally… you should set retry_max_attempts = 5 with min_delay_seconds = 1 in your HCL block. Coming from Zendesk, where API limits were looser, this strict backoff in Genesys Cloud is a necessary adjustment to avoid 429s.