Activity doesn't execute

[wq9578]

The workflow's execute() function is called, but not its first activity's execute() function.

The workflow class method starts with:

    public function execute($email_address = '')
    {
        dump(__CLASS__ . '::execute()', $email_address);

        yield ActivityStub::make(SendEmailAddressVerificationEmailActivity::class, $email_address);

and prints:

"App\Workflows\Tests\VerifyEmailAddress\VerifyEmailAddressWorkflow::execute()"
"test@example.com"

But the activity class method doesn't print or log anything:

    public function execute($email_address)
    {
        dump(__CLASS__ . '::execute()', $email_address);

        Log::info('Sending to: ' . $email_address);

In the workflows database table all started workflows have status waiting.
I'm using Laravel 10.

[rmcdaniel]

@wq9578 I'm sorry to hear that you're having an issue. I'm wondering, did you make sure to run the queue worker? Check that first and let me know if that wasn't the issue. Thanks!

Laravel Workflow uses Laravel's queued jobs to run workflows and activities in the background. You will need to either run the queue:work Artisan command or use Horizon to run your queue workers. This will process the queued workflows and activities and execute them in the background. Without a running queue worker, workflows and activities will not be executed.

(Source: https://laravel-workflow.com/docs/installation#running-workers)

[wq9578]

Of course I had started the queue (and I have tested it again now).

The exact instructions were:

1. Starting the server: php artisan serve
2. Starting the queue: php artisan queue:work

I also tried starting the queue first, and starting the queue only (without starting the server).

So what is the next step in debugging?
The library as well as the website are nicely done, as far as I can see, so I would like to use it.
Thanks!

[rmcdaniel]

@wq9578 Just wanted to cover the basics and also was wishful thinking on my part! 😂

What do you see in the output of php artisan queue:work? Anything? Also can you try using Log::info in both places? I think dump might not work in all cases.

Can you provide the entire workflow and activity classes? You can use https://gist.github.com/ or paste it here.

Also can you tell me what version of the library you are using? What queue driver? What database driver?

How are you starting the workflow and checking the output? Thanks in advance!

[wq9578]

See the files at https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71, and for the versions the log file there.

The queue doesn't report anything, even with maximum verbosity: php artisan queue:work -vvv.

Console:

php artisan test tests/Feature/EmailVerificationWorkflowTest.php
"App\Workflows\Tests\VerifyEmailAddress\VerifyEmailAddressWorkflow::execute(test@example.com)" // app/Workflows/Tests/VerifyEmailAddress/VerifyEmailAddressWorkflow.php:24

   PASS  Tests\Feature\EmailVerificationWorkflowTest
  ✓ it logs the PHP and composer version                                                                                                         0.11s  
  ✓ it logs the composer package versions with ('laravel/framework')                                                                             0.01s  
  ✓ it logs the composer package versions with ('doctrine/dbal')                                                                                 0.01s  
  ✓ it logs the composer package versions with ('pestphp/pest')                                                                                  0.01s  
  ✓ it logs the composer package versions with ('pestphp/pest-plugin-laravel')
  ✓ it logs the composer package versions with ('laravel-workflow/laravel-workflow')
  ✓ it test the email address verification workflow                                                                                              0.03s  

  Tests:    7 passed (7 assertions)
  Duration: 0.20s

[rmcdaniel]

@wq9578 Thanks for the additional details! It looks like you are executing this via a Pest test? Have you tried also making an artisan command to start the workflow that way? I'm going to try all of this myself but I want to narrow down if it's an issue running via Pest. All the tests I have just use vanilla PHPUnit btw. Also can you confirm which queue driver you are using? Is it redis or database or something else?

[wq9578]

I made a PHPUnit test to make sure that it isn't a Pest issue: https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71#file-emailverificationworkflowphpunittest-php
The result is still the same.

See the updated log here for the database engine version: https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71#file-laravel-log

[rmcdaniel]

@wq9578 That doesn't make sense because this library is tested with PHPUnit. All the tests run automatically in the GitHub pipeline. If this library didn't work with PHPUnit then the pipeline wouldn't work.

https://github.com/laravel-workflow/laravel-workflow/blob/master/tests/Feature/WorkflowTest.php

Try making a simple artisan command to start your workflow. There's something we're still missing here.

[rmcdaniel]

@wq9578 This is what I am using:

https://gist.github.com/rmcdaniel/e343a84954481eb069fb243bc078e956

[wq9578]

Artisan command: https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71#file-workflowtest-php

Nothing changed, as expected.
Both the MySQL database and Pest always worked fine and seamlessly with all other features of my current Laravel project.

[rmcdaniel]

@wq9578 I tested your workflow locally and it works for me. 😞

[wq9578]

Tried it with your console command (with minor modifications), didn't work either: https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71#file-workflow-php

$ php artisan workflow:run
"App\Workflows\Tests\VerifyEmailAddress\VerifyEmailAddressWorkflow::execute(test@example.com)" // app/Workflows/Tests/VerifyEmailAddress/VerifyEmailAddressWorkflow.php:24
^C

[rmcdaniel]

@wq9578 Do you have some time for a video chat so we can screen share? That would be the fastest way to make progress at this point. The major issue right now is that we aren't getting any error message. So we need to figure out when/where/how it's silently dying in the middle of the workflow.

[wq9578]

@rmcdaniel Thanks for your kind offer.
For arranging a video chat appointment, is there any way on GitHub you could tell me your email address privately?
I don't want to share contact details here.

[rmcdaniel]

Here's my public email address https://github.com/laravel-workflow/laravel-workflow/blob/master/composer.json#L27