Troubleshooting

Common issues encountered when using Opus, with resolution steps and verification checks.

Cannot access the platform

Symptom: The Opus management portal returns an error or does not load after TechPass authentication.

Cause: The device does not meet network requirements, or the Opus URLs are not whitelisted.

Resolution:

Confirm you are using a non-SE GSIB, SEED, or COMET machine.
Check that the Opus URLs are whitelisted on your network — refer to Service levels and network.
Clear browser cache and retry.

Verification: The Opus dashboard loads after login.

Symptom: The dashboard shows no projects after successful login.

Cause: The user has not been assigned to any projects by an administrator.

Resolution: Contact your organisation’s Opus administrator and request project assignment with the appropriate role (Editor or Viewer).

Verification: Projects appear on the dashboard after the administrator assigns you.

Workflow issues

Workflow simulation fails

Symptom: Selecting Simulate produces an error or the workflow does not execute.

Cause: One or more nodes have incomplete configuration, or mock data is missing for external integration nodes.

Resolution:

Check for validation error indicators on nodes in the workflow graph — these highlight incomplete configuration.
For nodes that call external systems, enable Mock Data in the node settings and provide sample JSON.
Non-mockable nodes (Decision, Decision Table, Expression, Function, Switch, Workflow, Delay, Extract, Convert) require real values — ensure valid test data is provided.

Verification: The simulation completes without errors and produces expected output.

Workflow exceeds node limit

Symptom: Adding a new node is rejected or the workflow fails to save.

Cause: The workflow has reached the 50-node limit.

Resolution:

Break the workflow into smaller reusable workflows using the Workflow node.
Consolidate logic into Function or Decision nodes where possible.

Verification: The workflow saves and simulates successfully after restructuring.

Payload too large

Symptom: Node execution fails with a payload size error.

Cause: The combined JSON payload from upstream nodes exceeds 10 MB.

Resolution:

Reduce the data being passed — filter or extract only the fields needed by downstream nodes.
Use the Storage node to persist large files separately from the data payload.

Verification: The node executes without a payload size error.

Decision issues

Decision nesting depth exceeded

Symptom: A decision referencing other decisions fails with a depth error.

Cause: The nesting exceeds 5 levels (decision A → B → C → D → E → F is rejected at level 6).

Resolution: Flatten the decision structure by inlining logic from intermediate decisions or restructuring the dependency chain.

Verification: The decision executes without a nesting depth error.

Publishing and release issues

Cannot publish — entity is not in draft

Symptom: The publish button is greyed out or the entity does not appear in the publish list.

Cause: The entity has not been modified since the last publish, or another user last modified it.

Resolution:

Confirm the entity has unsaved draft changes.
Only the user who last modified the entity (or an administrator) can publish it.

Verification: The entity appears in the publish list and can be selected.

Automations not working after release

Symptom: A workflow that worked in staging does not execute correctly in production.

Cause: The release was created before the latest changes were published, or the access token targets the wrong environment.

Resolution:

Confirm the latest changes are published.
Create a new release that includes the published changes.
Verify the access token is for the production environment, not staging.

Verification: The workflow executes correctly when called against the production endpoint.

Contact and support

If the issue persists after following the steps above:

Community: Microsoft Teams or Slack
Feedback: go.gov.sg/opus-feedback

When contacting support, include:

Workspace and project name
Workflow or decision name
Environment (staging or production)
Steps to reproduce the issue
Screenshots of any error messages or validation indicators

Opus core concepts

Release notes