Known Issues
Documented product issues that may affect configurator testing, along with their fixes or current status. For general how-to fixes, see Troubleshooting.
| Issue | Status |
|---|---|
Configurator: FUNCTIONALITY_NOT_ENABLED | Resolved (org configuration) |
Configurator: success=false on mutation | Under investigation |
Configurator: FUNCTIONALITY_NOT_ENABLED [IHeadlessConfiguratorFamily]
Symptom
Running a configurator snapshot (quote-anchor or scenario) fails at the very first configurator call with:
Failed to load configuration instance: FUNCTIONALITY_NOT_ENABLED:
This feature is not currently enabled for this user type or org: [IHeadlessConfiguratorFamily]
The run report shows an execution error and no configuration messages, because the Product Configurator Business APIs (for example load-instance) are rejected before any step runs.
Cause
The connected Salesforce user does not have the Product Configurator API User system permission. This is required for the headless/Business API configurator family, and it is independent of:
- The standard "Product Configurator" permission set
- The user's profile (even System Administrator)
- The API version
Fix
Create and assign a dedicated permission set:
- In Salesforce Setup, create a new Permission Set.
- Under System Permissions, enable Product Configurator API User.
- Assign the permission set to the connected/integration user used by Revsnap.
- Reconnect the org in Revsnap (or refresh the access token) so the change takes effect.
After assignment, re-run the configurator snapshot. load-instance should return a context and the run should proceed through its steps.
Resolved via org configuration, no application change required.
Configurator: Configurator API returned success=false
Symptom
After the load-instance permission issue is resolved, a scenario run reaches the first mutation step (for example Attempt: add Core Package) and fails with:
Configurator API returned success=false
The step is marked failed and no configuration messages are returned.
Cause
Under investigation. The configurator mutation API (add-nodes) returns a non-success response for the attempted action. This may be related to:
- The node path or relationship payload for the bundle component
- The product or selling-model details resolved for the added product
Fix
No confirmed fix yet. If you hit this error, capture the scenario name, snapshot, and run ID and contact support.
Under investigation.