Can anyone clarify the expected behavior when attempting to bulk-create agent scripts via the Platform API for a multi-org deployment? Our Premium App handles onboarding for several enterprise clients, and we are automating the creation of standardized script templates using POST /api/v2/agent-scripts.
We are encountering consistent 409 Conflict errors with the message “Resource already exists” when the script names match existing templates in the target organization, even though the IDs are different. The documentation suggests that script names must be unique within an organization, but our workflow requires generating scripts with identical naming conventions (e.g., “Standard Support Flow - v2”) for different departments within the same org.
Is there a supported workaround for this uniqueness constraint, or should we be implementing a suffix-based naming strategy in our Terraform modules? We want to avoid manual intervention for our clients in the US West region where these onboarding batches are frequent. Any insights on best practices for handling this in an automated provisioning pipeline would be appreciated.