Common Troubleshooting

TL;DR

A symptom-first index of the errors you are most likely to hit on the platform, grouped by area (login, registration, policy, simulation, approvals, monitoring, permissions, data). Each entry lists what you see, why it happens, and how to resolve it.

How to use this page

Find the section that matches where the error appeared (the page, dialog, or workflow step). Read the What you see line to confirm it matches your symptom, then follow the Resolution steps. If an error code is shown (e.g. API-13), search this page for that code.

Tip

Most "save failed" errors surface a banner at the top of the form. Hover the field labels with red outlines: the form-level message often explains the exact field that needs fixing.

"Invalid username or password"

What you see: Login form shows a red banner after submitting credentials.
Why: The username does not exist, the password is wrong, or the account is locked.
Resolution: Confirm the username is correct, reset the password if needed, and contact your admin if the account may be locked.

OTP / MFA failure

What you see: After entering credentials, the OTP step fails or times out.
Why: The OTP code was wrong, expired, or the OTP delivery channel (email/SMS) failed.
Resolution: Request a new code. If repeated codes do not arrive, contact your admin to verify the OTP provider is configured.

Session timeout / Unauthorized

What you see: Mid-session you are redirected to the login page or actions return 401 Unauthorized.
Why: Your access token has expired, or the OAuth2 / SAML session has been invalidated.
Resolution: Sign in again. If this happens repeatedly within minutes, ask your admin to check the configured session lifetime.

"Authentication method not configured"

What you see: The login screen does not show the expected OAuth2 or SAML button.
Why: The auth provider is not enabled or is misconfigured on the server.
Resolution: This is an admin-side fix. The admin must verify the provider entry in the user authentication config.

2. Registration errors (Tables, Data Elements, Features, Models)

"Cannot save primary DataTable without setting the primary column"

Where: Data Vault → Table details.
Why: A table marked as Primary must declare which column is the primary key.
Resolution: Open the table, select a column, and mark it as the primary column before saving.

"Duplicate parameter `{name}` found"

Where: Model or Algorithm registration.
Why: Two input or output parameters share the same name.
Resolution: Rename one of the duplicates. Parameter names must be unique within a single Model/Algorithm.

"Duplicate dataset alias found"

Where: Model registration, Training & Validation Data section.
Why: Two datasets are referenced under the same alias.
Resolution: Give each dataset a unique alias (for example, train, validation, holdout).

"This form has error(s), saving failed"

Where: Any registration form.
Why: One or more required fields are empty or contain invalid values.
Resolution: Scroll up and look for fields with red outlines. Hover the label to see the specific message.

"Invalid data type provided" (`API-63`)

Where: Saving a Feature, Data Element, or Model definition.
Why: A value's type does not match the declared parameter type (for example, a string is provided where a numeric is expected).
Resolution: Check the parameter's declared type and adjust the input expression or constant.

"Data Table Schema Error" (`API-66`)

Where: Registering a Table against an external source.
Why: A column declared in the registry does not exist in the source, or its type conflicts with the declared type.
Resolution: Refresh the column list from the source and reconcile the declared schema. Remove or rename columns that no longer exist upstream.

3. Policy and Strategy errors

"Invalid workflow status: `{status}`" (`API-13`)

What you see: Attempting to publish, archive, or revert a Policy fails with this message.
Why: The requested status transition is not allowed from the Policy's current state.
Resolution: Check the Policy's current status. Refer to the policy lifecycle for allowed transitions.

"The entity is in a status which does not allow modifications" (`API-14`)

What you see: Save or edit is blocked on a Policy.
Why: The Policy is in a locked state (Published, Archived, or under approval).
Resolution: Create a new version from the locked Policy and edit that version instead.

"Unable to change status to `{target}`: `{reason}`" (`API-57`)

What you see: A status transition is rejected with an explanatory reason.
Why: Common reasons include unsaved changes, missing required fields, or a pending approval.
Resolution: Read the reason text carefully. Save outstanding changes, complete the missing fields, or wait for the approval to clear.

"You have selected Action Rule, not allowed to add more configs"

Where: Strategy / Offer creation.
Why: An Action Rule must be the terminal step in a rule chain. Nothing can follow it.
Resolution: Remove the Action Rule if you need more steps, or move it to the end of the configuration.

Workflow validation errors

What you see: The workflow builder flags one or more nodes red.
Why: Common causes are missing-connection, invalid-rule, circular-dependency, unreachable-node, or invalid-strategy-config.
Resolution: Click the flagged node to see the specific message. Connect dangling ports, remove cycles, and ensure every node is reachable from the entry point.

4. Simulation errors

"Cannot save simulation which is already VERIFIED"

Why: A Verified simulation is immutable so that downstream comparisons remain reproducible.
Resolution: Clone the simulation and edit the clone.

"Cannot create a simulation as output-alias for `{entity}` not set"

Why: The underlying Model or Framework has no declared output alias, so the simulation cannot collect results.
Resolution: Open the Model/Framework, add an output alias, and re-run the simulation.

"Cannot delete simulation which is being used in data records"

Why: The simulation's output is referenced by one or more data records or test sets.
Resolution: Remove the dependent references first, or archive instead of deleting.

"Cannot remove comparison for What-If Analysis simulations"

Why: A What-If simulation always requires a baseline to compare against.
Resolution: Pick a different baseline rather than removing the comparison entirely.

"Cannot compare a simulation with itself"

Why: Baseline and candidate must be different simulations.
Resolution: Select a different baseline (or candidate) from the dropdown.

Forbidden keyword in SQL simulation

What you see: Simulation rejected with a "forbidden keyword" message.
Why: The SQL contains a blocked keyword (for example, DROP, DELETE, TRUNCATE). Simulations are read-only by design.
Resolution: Rewrite the query using SELECT-style read operations only.

5. Approval workflow errors

"Unable to send for approval: `{reason}`" (`API-51`)

What you see: The "Send for approval" action returns an explanatory reason.
Why: Typical causes are missing required fields, no approval framework assigned, or rules that fail validation.
Resolution: Address each item listed in the reason, save, and resubmit.

"Object Type `{type}` is not workflowable"

What you see: Attempting to attach an approval workflow to an entity is rejected.
Why: Approval workflows are supported only on specific object types (e.g. Policies, Models). Datasets and ad-hoc objects are not workflowable.
Resolution: Apply the workflow on a supported object type. See Configure an Approval Workflow.

Approval assignment fails

Why: The chosen user is not part of the responsibility group, or you lack permission to assign approvers.
Resolution: Ask an admin to add the user to the relevant approval group, or pick an eligible user.

6. Permissions and access

"User `{user}` does not have `{action}` access to `{entity}`" (HTTP 403)

What you see: An action button is greyed out, or the API responds with 403 Forbidden.
Why: You do not have Read, Write, Delete, or Publish permission on this object.
Resolution: Request access from the object's owner or your admin. Permissions are managed per-object.

"Email notification provider is not configured"

What you see: Setting up an alert that sends email fails to save.
Why: The platform has no SMTP / email provider configured.
Resolution: This is an admin-side fix. Configure an email provider in the platform settings before creating email-based alerts.

7. Data ingestion and parsing

"Failed to parse JSON" / "Failed to decode text content"

Where: Importing CSV, JSON, or uploading a definition file.
Why: The file is malformed or uses an unsupported encoding.
Resolution: Validate the file in your editor (UTF-8, valid JSON), then retry.

"Unable to fetch columns: `{error}`"

Where: Registering or refreshing a Data Table.
Why: The platform cannot reach the source, or credentials have changed.
Resolution: Verify the connection in Data Vault. Test connectivity with your admin if needed.

"No data found for given id"

Where: Opening a Data Element / Table / Feature by URL or after a refresh.
Why: The object was deleted, or the ID in the URL is wrong.
Resolution: Return to the listing page and re-open the object. Check Trash if soft-delete is enabled.

"Invalid definition" (`API-65`)

Where: Importing a JSON / YAML definition.
Why: The definition does not match the expected schema for the object type.
Resolution: Compare against an export from a working object of the same type, fix the offending keys, and reimport.

8. Monitoring, dashboards, and alerts

"Failed to refresh data"

Where: A dashboard tile or report.
Why: The underlying data source is unavailable, the query timed out, or the schema has changed.
Resolution: Retry the refresh. If it keeps failing, open the report definition and verify the columns still exist.

"Failed to export data"

Where: Exporting a report from a dashboard.
Why: The export format is incompatible with the data, or the file is too large.
Resolution: Try a smaller date range or a different format (CSV instead of Excel).

"Failed to delete alert as it has been triggered `{N}` times"

Why: Alerts with trigger history are retained for audit purposes.
Resolution: Disable the alert instead of deleting it, or archive the alert's history first if your role allows it.

Invalid email format in alert recipients

What you see: Alert save fails with a red outline on the To/Cc/Bcc field.
Why: One of the listed emails is malformed.
Resolution: Use comma-separated, properly formed email addresses (e.g. name@domain.com).

9. Generic API errors

These codes can surface from many actions. The text after the code is the most useful clue.

"{message}" (`API-11`)

Why: A generic, server-side error that did not match a more specific code.
Resolution: Read the message verbatim. If it is unclear, capture it along with the action you took and share with support.

"The request is invalid. Reason: `{reason}`" (`API-12`)

Why: The request body or query parameters do not match what the endpoint expects (missing field, wrong type, malformed JSON).
Resolution: Check the reason text for the specific field at fault. If you are calling the API directly, validate against the endpoint's schema.

"Validation failed: `{details}`" (`API-52`)

Why: One or more fields failed schema validation (length, regex, enum value, required, etc.).
Resolution: Each item in details names the field and rule that failed. Fix the listed fields and resubmit.

"Internal Server Error: `{details}`" (`API-54`)

Why: An unhandled exception on the server. This is usually a bug, not user error.
Resolution: Retry the action once. If it persists, capture the full error text, the time, and the action taken, and share with support.

"Invalid input(s) provided: `{details}`" (`API-67`)

Why: Inputs to an action (e.g. running a simulation, registering an object) are individually valid but inconsistent with each other or with the target object.
Resolution: Read details for the offending input. Common cases: an input alias not present on the target Model, a parameter typed differently than declared.

10. Execution and run-time errors

These come from artifact execution (a Feature being evaluated, a Model being scored, a Policy being simulated) rather than from saving definitions.

Execution dependency error

What you see: A run fails citing a missing or unresolvable dependency.
Why: An upstream object (Feature, Model, Data Element) referenced by the running artifact is missing, archived, or has not been built.
Resolution: Open the failing artifact, identify the upstream reference in the error message, and republish or rebuild it.

Execution runtime error

What you see: The run reports the exception type and message from the artifact's own code (for example, KeyError: 'col_x', ZeroDivisionError).
Why: A bug or unexpected input in the artifact's expression or model code.
Resolution: Reproduce on a small sample, fix the expression or model code, and rerun.

"Zero records found"

What you see: Sample generation or a simulation completes but returns no rows.
Why: Filters, joins, or the time window leave the result set empty.
Resolution: Widen the filter, check that the source table actually has rows in the selected period, and verify join keys.

Step partial success

What you see: A job step ends with a "partial success" status with N failed records.
Why: Some input records hit a per-record error (bad value, missing input) while others passed.
Resolution: Open the step logs, inspect the failing records, and clean the source data or harden the artifact to handle the edge case.

11. Resources, artifacts, and configs

"Invalid product deployment configuration" (`API-58`)

Where: Publishing or deploying a Product.
Why: Required fields in the deployment config are missing, or referenced resources are not valid.
Resolution: Open the deployment config, complete the missing fields, and verify every referenced object exists and is published.

"Artifact creation failed: `{error}`"

Where: Building an artifact bundle (e.g. for a Model or Framework).
Why: Missing dependencies, invalid Python / definition syntax, or a compilation error in the bundled code.
Resolution: Read the error text for the underlying cause. Fix the dependency or syntax error and rebuild.

"Invalid delete request for Config" (`API-71`)

Where: Deleting a config item.
Why: The config is in use elsewhere, is referenced by another object, or is a system-managed config.
Resolution: Find and remove the references first, or leave system configs untouched.

"Transform not found"

Where: Opening a Dataset or Model that uses a transform.
Why: The transform was deleted or renamed while still referenced.
Resolution: Reattach a valid transform, or recreate the missing one.

Still stuck?

If your symptom is not listed, capture the following before contacting support:

The exact error text (or screenshot).
The error code, if present (e.g. API-13).
The object type and ID you were working on.
The action you took just before the error appeared.