Architect Data Action 403 Forbidden with Service Account During Load Test

  • Genesys Cloud US1
  • JMeter 5.6
  • 500 concurrent threads
  • Service Account with Admin permissions

What is the correct way to configure OAuth scopes for a Service Account used in Architect Data Actions during high-concurrency load tests? The test returns HTTP 403 Forbidden when attempting to access flow data. Standard user tokens work fine, but the service account fails immediately when JMeter ramps up. Is there a specific rate limit or scope requirement I am missing for automated flows?

1 Like