📄️ About state management
In Taskurai, all Tasks and Steps are persisted to guarantee a durable and stateful operation. However, tasks and steps are stored in the central database and are subject to size limits depending on the subscription plan. They are meant to maintain initialization and configuration data and return values. Large initialization and return data should be stored in a state store and referenced in the tasks and steps.
📄️ Deploying state stores
In this section, you'll learn how to set up an internal state store.
📄️ Storing state
This section provides information on how to store or update state.
📄️ Retrieving state
This section provides information on how to retrieve previously created tasks.
📄️ Listing state
This section provides information on how to list state entries.
📄️ Deleting state
This section provides information on how to delete state.
📄️ Storing initial task state
This section provides information on how to store initial state for a task in the client application. This state can be linked to task arguments and used in a command.
📄️ Managing state in commands
This section provides information on how to access state in commands and to store intermediate and final state in the worker application.
📄️ Managing state in steps
This section provides information on how to access state in steps and to store intermediate and final state. This state can be linked to step arguments and used as a step or task output.
📄️ Advanced state options
State stores offer some advanced configuration in case your application requires stricter control on concurrency and consistency.
📄️ State store configuration
In this section, you will learn how to set up state stores in Taskurai.