Skip to content

Troubleshooting actions

This topic describes how to use the Developer Tools provider by the browser to troubleshoot issues with apps.

Finding out which action in an action set is failing

When there are multiple actions in an action set then an OnFailure response from the provider will prevent all the actions in the set from running. Use the Developer Tools in your browser to work out which action is failing.

  1. In Chrome, open the Developer Tools.
  2. In the Name column, click the last invoke.
  3. Go to the Preview tab.
  4. Expand responsesInOrder and then expand each response (action).
  5. The outcomeStatus is either OnSuccess or OnFailure. For OnFailure, there will be an error message.

on_failure_response_for_actionset

Figure: Identifying failing actions

How to view the topic data in the response from the provider

You can use the Developer Tools in your browser to verify whether an action is returning any topic data.

  1. In Chrome, open the Developer Tools.
  2. In the Name column, click the last invoke.
  3. Go to the Preview tab.
  4. Expand responsesInOrder and then find the response (action).
  5. Expand topicData.

    For example, for a data grid there will be an entry for each row on the page (default page size is 10) and one entry for a form.

topic_data

Figure: Viewing the topic data in the response

Subscription issues: No properties have been requested

Any component, element or UI element that subscribes to an action must be configured with an appropriate data type matching the action response.

For example, if a component containing a Text Area needs to subscribe to an action that returns a message text then the data source of the Text Area must be set to the appropriate provider type. If no provider type is set on the Text Area then this error is displayed: No properties have been requested.

Note: When an action is published but has no corresponding subscription, the OnSuccess event will not fire. This causes downstream actions.