Free cookie consent management tool by TermsFeed Testing Offline Actions and Tasks [Offline Mobile]
Testing Offline Actions and Tasks
The capabilities described on this page are included in Appian's advanced and premium capability tiers. Usage limits may apply.


As you create and update your offline interfaces, you will need to test them on a mobile device to make sure that everything works without any errors.

This document outlines how to test and troubleshoot offline actions and tasks after you have created them.


In order to test offline interfaces, you need to:

Test the action or task on a mobile device

You cannot test offline functionality on the desktop. You need to test offline forms on a mobile device using the Appian mobile application.

Tip:  Offline mobile errors will not occur on the desktop. Additionally, if there are offline mobile errors, they will appear on mobile whether your device is online or offline.

To test on a mobile device:

  1. Make sure your changes are saved.
  2. On a mobile device, open the Appian mobile application.
  3. Go to your site and open the site page with the action or the task list.

    Note:  IMPORTANT: You do not need to go offline to test the interface. The interface will behave the same way whether it is offline or not.

  4. Pull down to refresh the interface.

    screenshot of refreshing the offline form

  5. Fill out all of the fields, whether they are required or not. Go through every screen to the final submission.

    Note:  IMPORTANT: Test the entire action or task completely, including all fields, or users may run into issues at runtime that will cause them to lose their work.

  6. If an error like the following appears, troubleshoot it.

    screenshot of a System Error dialog

  7. After troubleshooting the error, save changes and refresh the page.

Troubleshoot offline mobile forms

If the offline mobile action or task returns an error, troubleshoot it using the following guidance.

Make sure you are following the design best practices

The error message contains the interface name and line number that caused the issue.

Check the line number in the interface expression to see if there is:

Try the steps on desktop

If you don't see any issues in the interface expression, try performing the same steps on the desktop version of the interface.

The desktop interface doesn't use the offline mobile evaluator. So if you get the same error on desktop, it may not be caused by offline mobile behavior. It may be caused by a general expression syntax error. Check around the line number in the interface expression to see if there is anything that could be causing the error.

Testing Offline Actions and Tasks