> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/development/flow-studio/applications/workflow/offline-workflow/create-an-offline-transactions.md).

# Create offline transactions

All machine step that writes data to a system must be placed in an offline workflow and in a swimlane where mode is set to machine. It is possible to either use the split step or end the workflow in the machine swimlane. A transaction will be created for every swimlane crossing that is executed.  

The offline transactions will be transferred the next time the device is online.

If the user signs out from the device before getting online, the transactions are saved and will be transferred the next time the same user is signed in and online. Not transferred transaction will however be removed if the devise is disconnected from the server.  

![](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-osmJsiTnFKxhGmPaD%2F-M-osx-xOzh9_TB_kOn8%2Fhelp_root_applications_workflow_offline_offlineTransactionsSteps.png?alt=media\&token=2b29cee5-8679-402e-9f43-5b9b99d00bf6)

![](https://529897662-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-osmJsiTnFKxhGmPaD%2F-M-ot2-xHSV2oXXZNpvs%2Fhelp_root_applications_workflow_offline_exampleWf2.png?alt=media\&token=abbb7866-8d68-4f72-b9f6-ce402de5f7aa)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.novacuraflow.com/development/flow-studio/applications/workflow/offline-workflow/create-an-offline-transactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.