Running Sessions

Sessions are run from the Sessions workspace. You can monitor a Session as it is running, and watch the progress of each individual task.

Run a Session

Navigate to the Sessions workspace.
From the Navigation Pane, select a Session to run.
Click the Play button in the Session toolbar to run the Session.

The following controls are available from the top bar of the Sessions workspace:

	The play button starts a Session, or resumes a paused Session.
	The pause button suspends a currently running Session.
	The stop button discards all data and results, and rewinds to the beginning of the Session.
	The rewind button rewinds the most recently performed task within a Session. Note: You can also rewind to any task by right-clicking it and selecting ‘Rewind’
Session Indicator	To the right of the stop button is the Session Indicator. This displays the current status of the Session eg. Not Started, Paused, Error, Rewinding, etc

Note: The ability to rewind a Session is disabled when using Production Mode.

When a Session has completed, it is no longer possible to rewind tasks.

Note: Ending a Session with a Pause Task, allows the Session to stay "open" while the final Pause task has not completed.

While "open" all intermediate data is stored in the Session cache, allowing further Tasks to be added, Task Results to be viewed and downloaded, and the Map Viewer to be explored.

Monitoring Progress

The status of each task is indicated by an icon on the right-hand side of its entry in the task list:

	Task is currently running
	Task is paused
	The task is disabled and has been skipped
	Task is completed

Note: Before the task has started, no icon is displayed.

Similarly, the status of a Session is indicated by its icon in the Navigation Pane:

	Session is not yet running.
	Session is running.
	Session is paused.
	Session is completed.
	Session contains a Map ready for viewing.
	Session has failed.

Updating a Session in Progress

While a Session is running you can not insert, delete, or edit Tasks. When paused, a Session can have additional Tasks added to the queue, after the point at which it is paused.

A Session in progress will need to be stopped if changes need to be made to the Data Store or to any geometry definitions such as the CRS or the Z or M selection.

Data Stores will need to be refreshed and the Data Store Task will need to be run again in the Session.

Geometry definition changes will require the Schema Mapping to be refreshed or re-mapped in the Data Store.

Example: The Delimiter Separated Values (DSV) Data Store will require the mappings to be deleted and reconfigured when changing the attribute that holds the geometry.