Running a data app

Learn how to run data apps on Intersect, manually, or on a schedule.

Once you've built and published, its time to RUN your data app!

When you run an app, the data is basically launched through the app to be processed by all of the function blocks. Whether manually run, or run according to a schedule, each run represents updated results for that point in time.

In this tutorial:

Running an app

Data apps are ran from the App Mission Control.

A preview of the App Mission Control section in Intersect Labs

When the "Run App" button is clicked, you are automatically redirected to the published view. The data App automatically processes the data, stopping only when interactive blocks require user prompting.

From there, you can generate a share link and share the results of this particular run with anyone (whether they are registered with Intersect or not) by clicking on the Share Run Results button.

Running and sharing a data app in Intersect

App run logs

Back on the App Mission Control, a history bank keeps track of every run instance. Each run is documented along with the account holder that carried out the run, and the date and time of the run.

This run log allows you to revisit previous runs, and compare results either based on changes in the data set, or changes in the app itself.

Every time the data app is edited, these changes need to be published and re-ran to reveal these changes in your results. Each run is documented in this side panel so you can see who ran the app and when. However, this history bank allows you to return to a previous run to view past versions of your data app.

You might be wondering: what’s the purpose of running an app repeatedly? In most cases, data apps are pulling data sets from an external database, and therefore a new run is required each time the data set changes or updates.

However in some cases, with static input datasets, running the app repeatedly can offer other value such as identifying bugs within the app itself.

Run Errors

If a run instance fails, and an error is found, a red error symbol will show up in the run log. The error is identified in greater detail in the published view.

To find out how to automate this run process by scheduling your app to run on its own, check out the Scheduling tutorial video.