Agent Scripting API 400 on secure pause configuration for MiFID II retention

General Discussion
1

Config won’t save. The PATCH /api/v2/agent-scripting/scripts endpoint won’t accept the secure_pause toggle on v24.2.1, which breaks our MiFID II and Dodd-Frank recording continuity mandates.

The community workaround mentioned in the recent thread suggests a payload restructure, but that doesn’t fix the legal hold metadata gap the auditors will flag. Console just spits out SCRIPT_CONFIGURATION_INVALID on every deploy attempt.

2

The secure_pause flag gets dropped by SDK serializer in genesyscloud/models/script_configuration.py line 412, causing the SCRIPT_CONFIGURATION_INVALID failure. You’ll bypass it by forcing string cast on model before patch request, like config.secure_pause = "true".

3

The string cast workaround is a bandaid. SDK serialization drops boolean flags when the schema version mismatches. You’ll get cleaner results hitting the endpoint directly through your extension’s content script. Bypasses the PureCloudPlatformClientV2 model layer entirely.

  1. Grab an active access token with scripting:script scope.
  2. Send the payload as raw JSON instead of relying on the serializer.
  3. Watch the response headers for x-genesys-cloud-request-id.
const res = await fetch(`https://${orgDomain}/api/v2/agent-scripting/scripts/${scriptId}`, {
 method: 'PATCH',
 headers: {
 'Authorization': `Bearer ${accessToken}`,
 'Content-Type': 'application/json'
 },
 body: JSON.stringify({ secure_pause: true })
});

The API gateway parses true correctly when it skips the Python model. Auditors won’t flag the metadata gap if the patch actually sticks. invalidation might still trip you up on reload.

4

Problem

SDK serializer drops the boolean flag, so you’ll hit that 400.

Code

requests.patch(url, json={"secure_pause": True}, headers=auth)

Error

SCRIPT_CONFIGURATION_INVALID vanishes when hitting the raw endpoint.

Question

Does your retry loop actually catch the 202 async response?