Pushed the updated data masking profile via Terraform v1.49.0 to mypurecloud.com.au early Tuesday PST. The apply ran clean. Architect flow version 22 deploys the new regex patterns for AU mobile numbers, starting with 04. Console marks the compliance profile as active across the Sydney edge. It’s completely different from the Melbourne setup. The ACMA recording consent step triggers fine, but the actual masking drops when the recording hits the analytics bucket.
Querying the /api/v2/analytics/conversations/details/query endpoint returns a 422 Unprocessable Entity. The payload shows {“code”:“DATA_MASKING_APPLY_FAILED”,“message”:“Regex pattern mismatch for region AU-NSW”,“traceId”:“syd-edge-7742”}. The latency from LA to Sydney is sitting around 180ms, which shouldn’t break regex evaluation. The flow step just times out waiting for the masking service to acknowledge the payload. We’ve tried tweaking the timeout settings in the flow, but the console just shows the step as skipped.
The number porting registry syncs fine, so it’s not a routing issue. The masking profile definitely has the correct ACMA consent flags enabled. Running a local test against the /api/v2/data-masking/test endpoint works perfectly. It’s only failing once the call hits the recording storage tier. The regex for ^04[0-9]{8}$ is standard. Maybe the Sydney edge cache is holding onto an old profile version.
Logs from the flow execution:
{
"stepId": "mask_pii_au",
"status": "failed",
"error": "DATA_MASKING_APPLY_FAILED",
"region": "syd-edge",
"traceId": "syd-edge-7742"
}