Looking for some advice on troubleshooting this configuration error while migrating GDPR compliance settings from Zendesk to Genesys Cloud. We are currently in the final phase of moving our European support operations to GC, specifically handling the PII masking requirements that were previously managed via Zendesk’s built-in privacy fields. The goal is to replicate the automatic redaction of email addresses and phone numbers in interaction transcripts using Genesys Cloud’s Data Masking features within the Architect flow. When attempting to apply the standard GDPR masking template via the POST /api/v2/architect/flows endpoint, the API returns a 400 Bad Request with the specific error code InvalidConfiguration. The payload includes the correct masking rules for email and phone data types, matching the Zendesk field mappings we established in the previous phase. However, the validation fails on the actions array where the mask-data step is defined. The error message suggests that the masking-rule-id is invalid, yet we are using the system-generated IDs from the GET /api/v2/data/masking-rules endpoint. We have verified that the tenant settings for GDPR compliance are enabled and that the user account executing the API call has the Admin role with Data Masking permissions. The issue persists even when using a minimal flow with only the masking action and a disconnect node. This is blocking our compliance sign-off, as we need to ensure that all historical and new interactions are masked consistently with our previous Zendesk setup. The documentation states that these rules should be available out-of-the-box for EU tenants, but we are seeing this validation failure consistently. Any insights into why the system-generated masking rule IDs are being rejected during flow creation would be appreciated. Is there a specific sequence for enabling these rules before they can be referenced in an Architect flow?