Hello,
The SailPoint CLI transform preview command returns a 400.1 Bad request content error when it is executed against our Identity Security Cloud Sandbox tenant.
The preview previously worked in the Sandbox tenant. The same command and transform definition still work successfully against our Production tenant.
Environment
- Product: Identity Security Cloud
- SailPoint CLI version:
2.2.10 - Affected environment: Sandbox
- Production environment: Working as expected
- Previously working in Sandbox: Yes
- Recent configuration changes: None that we are aware of
What we tried
We executed the following command from PowerShell:
sail transform preview `
--file "C:\transform\20260713\create_transform_mail.json" `
--env <sandbox-environment-name>
The transform file contains the following JSON:
{
"name": "mail",
"type": "identityAttribute",
"attributes": {
"name": "email"
}
}
We also executed the same preview against our Production tenant. It works successfully in Production, but consistently fails in Sandbox.
Actual result
The command returns the following error:
Error:
Issues calling API
Response body:
{
"causes": [],
"detailCode": "400.1 Bad request content",
"messages": [
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The request was syntactically correct but its content is semantically invalid."
},
{
"locale": "und",
"localeOrigin": "REQUEST",
"text": "The request was syntactically correct but its content is semantically invalid."
}
],
"trackingId": "dcfe100114a742278fef70472672790f"
}
The response headers also include:
X-Sailpoint-Route-Version: beta
Expected result
We expect the CLI to evaluate the transform and return the preview result, as it previously did in Sandbox and still does in Production.
Additional information
- The Transform Preview feature had been working in Sandbox for several months.
- We are not aware of any tenant or CLI configuration changes made immediately before the issue started.
- Before the issue occurred, the CLI command was interrupted several times using
Ctrl+C. - There is currently no known workaround.
- The issue is reproducible in Sandbox.
- Production is not affected.
Questions
- What conditions can cause the Transform Preview API to return
400.1 Bad request contentwhen the JSON itself is syntactically valid? - Could this be caused by tenant-specific Transform Preview state or a service-side issue in the Sandbox tenant?
- Does the CLI maintain any local cache or temporary state that should be cleared?
- Could interrupting preview commands with
Ctrl+Cleave any local or server-side preview state that needs to be reset? - Is there a debug or verbose option that can show the actual request body sent by the CLI or provide more details about which content is considered semantically invalid?
- Has anyone encountered this error in only one tenant while the same command works in another tenant?
Any guidance on additional troubleshooting steps would be appreciated.
Thank you.