ServiceNow Data Action 429 Too Many Requests during GDPR Purge

Looking for advice on handling rate limiting when invoking ServiceNow via Genesys Cloud Data Actions for automated GDPR erasure. The webhook.execute node returns a 429 Too Many Requests error when processing bulk deletion tasks from Architect. Our London-based instance pushes payloads at 50ms intervals. Is there a native retry mechanism in the Data Action configuration or should we implement exponential backoff in the ServiceNow script include?