Troubleshoot a problem

Administrators assign roles that limit users' access to different functions. Depending on the role assigned, users might not see certain items in the main menu, network composer, or side menu. If you cannot see an item that you should see based on a role, verify that you are assigned the correct role. If you still cannot see the appropriate menu items, work with your System Administrator to ensure that you are assigned the correct roles and permissions.

If you are looking for an item you added or for the edits you made to an item, you might not see them right away. A banner message displays that confirms your updates will display shortly. If you want to see the updates, wait a minute or two before refreshing the page, and your updates will be reflected.

If an OPUS Action does not execute, verify the following:

• The OPUS Action is active.

• The correct OPUS Event is configured.

• The configured event occurred.

• The Solution, Process Network, or Agent binding matches the event context.

If an unexpected OPUS action executes, verify the following:

• The correct event is configured for each active OPUS Action.

• The Solution bindings match the expected event context.

• The Process Network bindings match the expected event context.

• The Agent bindings match the expected event context.

If an Agent is not invoked, verify the following:

• The OPUS Action executed.

• The Agent binding is configured correctly.

• The JavaScript explicitly calls ctx.api.agent.invoke(...).

• The Agent configuration is valid for the OPUS Action.

An Agent binding does not automatically invoke the Agent.

If the Event payload does not contain the expected data, verify the following:

• The correct OPUS Event is configured.

• The JavaScript uses ctx.opusEventPayload to access the payload.

• The JavaScript uses fields available in the payload for the configured Event.

• If a GraphQL call fails, verify the following:

• The GraphQL query or mutation is correct.

• The Integration Principal has the required permissions.

• The target business-object configuration is correct.

• Required header overrides are configured.

• The returned success, response, and errorString values do not indicate an error.

If an event call fails, verify the following:

• The target event is correct.

• The target app is correct.

• The request payload is correct.

• Required header overrides are configured.

• The Integration Principal has the required permissions.

If a business operation succeeds but a POST_OPERATION OPUS Action fails, the completed business operation remains successful. The OPUS Action runs after the underlying business operation completes and does not roll back the completed operation.

Troubleshoot the OPUS Action separately from the original business operation.

If other OPUS Actions do not execute after an action fails, verify the following:

• The failed OPUS Action does not contain an unhandled error.

• Appropriate error handling is included in the JavaScript.

• Logging provides enough information to identify the failure.

An unhandled error might prevent remaining OPUS Actions associated with the same event from executing.