📄️ Publishing Config
This will create a workflows.php configuration file in your config folder.
📄️ Options
There are various options available when defining your workflows and activities. These options include the number of times a workflow or activity may be attempted before it fails, the connection and queue, and the maximum number of seconds it is allowed to run.
📄️ Ensuring Same Server
To ensure that your activities run on the same server so that they can share data using the local file system, you can use the $queue property on your workflow and activity classes. Set the $queue property to the name of a dedicated queue that is only processed by the desired server.
📄️ Database Connection
Here is an overview of the steps needed to customize the database connection used for the workflow v2 durable models. This is only required if you want to use a different database connection than the default connection you specified for your Laravel application.
📄️ Customization Matrix
Frozen support matrix for Durable Workflow v2 model overrides, serializer settings, observability repository replacement, health, imports, migrations, and write-side behavior.
📄️ Microservices
Workflows can span multiple Laravel applications. One app defines workflows, another defines activities. Both share a database and queue, each running its own queue:work process.
📄️ Pruning Workflows
Workflow v2 separates two distinct lifecycle operations: