Data Action Timeout during WFM Schedule Publish via Integrations

Ran into a weird issue today with the new Data Action integration we set up to sync WFM schedule changes to our external HRIS. We are using Genesys Cloud 2024.4 in US-East-1. The goal is to trigger a specific Data Action whenever a schedule is published, pulling the agent ID and shift details to update our external system in real-time. The setup works perfectly for small batches, but when we publish the weekly schedule for our Chicago team (over 400 agents), the Data Action fails intermittently.

The error occurs at the /api/v2/integrations/data-actions endpoint. We see a 504 Gateway Timeout in the integration logs, but the WFM schedule publish itself succeeds without error. It seems the WFM publish event triggers the Data Action, but the payload processing or the external HTTP call times out before Genesys marks the integration task as complete. We have increased the timeout in the Data Action configuration to 30 seconds, which is the maximum allowed, but it still fails for about 15% of the agents during the bulk publish.

We are using the standard REST API client for the external call. The external endpoint responds in under 200ms when tested manually via Postman. Is there a known limit on the number of concurrent Data Action executions triggered by a single WFM publish event? Or is there a way to batch these requests within the Data Action configuration to avoid hitting the gateway timeout? We need this sync to be reliable for payroll processing. Any insights on how to handle bulk events in Data Actions would be appreciated. Thanks.