Skip to content

Race condition when starting a workflow within a database transaction #157

@Naugrimm

Description

@Naugrimm

When you create and start a workflow from within a database transaction, there is a chance hat this workflow will never be executed.

Please see the following test: Naugrimm/laravel-workflow: failing test

Our current workaround is placing all workflows in a special queue that has 'after_commit' => true enabled in config/queue.php.

If this is your preferred way, I would like to request an addition to the documentation.

Another (potentially BC breaking change) would be to set the $afterCommit property in the Activity/Workflow classes, similar to the connection and queue properties.

What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy