📄️ 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 stored workflow models. This is only required if you want to use a different database connection than the default connection you specified for your Laravel application.
📄️ Microservices
Workflows can span across multiple Laravel applications. For instance, a workflow might exist in one microservice while its corresponding activity resides in another.
📄️ Pruning Workflows
Sometimes you may want to periodically delete completed workflows that are no longer needed. To accomplish this, you may use the model:prune artisan command.