I can’t seem to figure out why the Genesys Cloud Data Action is timing out when attempting to map complex Zendesk ticket metadata during the initial migration phase. The specific issue arises when trying to replicate the hierarchical tag structure from Zendesk into Genesys Cloud custom attributes via a Data Action in Architect. In Zendesk, we utilized nested tags for SLA prioritization, but Genesys Cloud requires flat key-value pairs. I have constructed a Data Action using the genesyscloud:data:put operation to push this data, but it consistently fails with a 504 Gateway Timeout error after exactly 60 seconds. The payload size is minimal, under 2KB, so network latency in the Europe/Paris region should not be the culprit. The Architect flow logs show the request being sent correctly, but no response is ever received from the Genesys Cloud API endpoint /api/v2/attributes/values. I have verified that the OAuth token used in the Data Action has the admin:attribute scope, and the target attribute group exists and is active. Comparing this to Zendesk’s API, which handles bulk updates much more gracefully, this feels like a limitation in the Data Action’s HTTP client configuration. I have tried increasing the timeout in the Data Action settings to 120 seconds, but the error persists at the 60-second mark, suggesting a hard limit somewhere in the platform or the specific integration module. The environment is Genesys Cloud US-East, and we are using the latest version of the Architect UI. Is there a known limitation on Data Action execution time for attribute updates, or should I be using a different integration method like a custom Connect app to handle this mapping? The migration timeline is tight, and this block is preventing us from finalizing the agent workspace configuration.