# Offline workflow

**Two different levels of offline:**

**Built-in semi-offline:**

* The fat clients only need connectivity when passing a cogwheel.
* Seed inbox items are downloaded and can be accessed without connectivity.
* Less network dependency and better mobile performance.
* Push cogwheels to the start and end events ? and you can be offline in between.

**Constant offline:**

* Offline Resources are used for supporting data (User Info, Equipment Structures, Lists etc.)
* Machine Swimlanes executes cogwheels on the server.
* A background job on the client handles data and transactions whenever there is connectivity.
* The user do not have to think about going online or offline.

![](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-onOWJmJDlgONGcw8O%2F-M-ooe4BjudUu2tlyjuF%2Fhelp_root_applications_workflow_offline_exampleWf.png?alt=media\&token=d43d2284-9867-44b7-a22a-d4d904762fb3)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.novacuraflow.com/development/flow-studio/applications/workflow/offline-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.