My configuration keeps failing when attempting to replicate Zendesk macros as Genesys Cloud Agent Scripts via the API. We are migrating a high-volume support team from Zendesk Support to Genesys Cloud, aiming to replace static macro templates with dynamic, context-aware scripts. The Zendesk macros contain specific HTML formatting and dynamic variable placeholders like {{ticket.requester.name}} that we are trying to map to Genesys Cloud {{contact.attribute.name}} equivalents. When posting to /api/v2/scripts, we receive a 400 Bad Request with the error message Invalid script content structure. The payload includes the sections array with paragraph blocks, but the validation fails on the richText content type. We have verified the JSON structure against the OpenAPI spec, and the script ID generation seems correct. Is there a specific limitation on HTML tags within script paragraphs in Genesys Cloud that differs from Zendesk’s macro rendering engine? We are using the latest REST API version and have admin permissions for script management.