Jobs queued with Model Id 0

[jasontxf]

• Horizon Version: 5.10.5
• Laravel Version: 9.43.0
• PHP Version: 8.1.5
• Redis Driver & Version: predis/phpredis (How do I check in forge? Not in composer.json) Redis version: 5.0.7
• Database Driver & Version: mysql 8.0.21

Description:

When queueing jobs with a model, the queued job model id becomes 0 which resulted in the actual queued job not being able to be processed.

It doesn't happen all the time, but it happened frequently enough to become a problem for me. This happened right after I upgraded Laravel to 9.43.0. Previously it was working 100% of the time

Steps To Reproduce:

I merely queue it the normal way.

app(SendTelegramMessage::class)
    ->dispatch($log);

I have no idea how to troubleshoot further as it's not happening all the time.
Any help/clues will be greatly appreciated. Thanks!

[ankurk91]

What is the schema for App\MessageLog table?
How are you dispatching this job?

Can you share code your for this job? Specially constructor

[jasontxf]

Hello,

Thanks for replying!

Here's the Schema for MessageLog Table

Schema::create('message_logs', function (Blueprint $table) {
			$table->id();
			$table->foreignId('user_id')->nullable()->constrained()->onDelete('cascade');
			$table->string('channel')->index(); 
			$table->string('source')->index(); 
			$table->text('message')->nullable();
			$table->text('referrer')->nullable();
			$table->json('payload')->nullable();
			$table->json('headers')->nullable();
			$table->timestamps();
		});

Just a very typical model.

I dispatched the job using the following code as stated above

app(SendTelegramMessage::class)
    ->dispatch($log);

The constructor for the jobs looks like this

<?php

namespace App\Jobs;

class SendTelegramMessage implements ShouldQueue
{
    use Dispatchable;
    use InteractsWithQueue;
    use Queueable;
    use SerializesModels;

    /**
     * @var TelegramChat
     */
    public $log;
    
    /**
     * Create a new job instance.
     *
     * @param  MessageLog  $log
     */
    public function __construct(MessageLog $log)
    {
        $this->queue = 'message';
        
        $this->log = $log;
    }

}

Hope it helps!

[henzeb]

Did you save the model first?

[jasontxf]

Hi,

Yeah, I did. Only after the model is created, then i dispatched it. Here's the code for the send function

  public function send($message, array $options = null)
  {
      $log = app(MessageLog::class)
          ->createTelegramLog($message, $this, $options);

      app(SendTelegramMessage::class)
          ->dispatch($log);
    }

and within the @createTelegramLog method

   public function createTelegramLog($text, TelegramChat $chat, $options = [])
    {
        return self::create([...]);
    }

This issue happened every now and then which is why it really puzzles me so much.
Thanks for taking a look!

[ankurk91]

Can you try this

app(SendTelegramMessage::class)
          ->dispatch($log->refresh());

[jasontxf]

That's a good idea! I'll give this a try and update again. Thanks!

[jasontxf]

Sadly, it's still happening :(

Really have no clue why is this happening.

[lioneaglesolutions]

I am having the same issue... no idea what the cause is. It seems to happen randomly. @jasontxf any luck fixing it?

[lioneaglesolutions]

Seems to happen if webhooks are received in quick succession but not always.

Any similarities there?

[jasontxf]

It happened randomly but often enough. So when you are receiving many webhooks simultaneously, the chances of it happening are higher. So you will be able to see it happen.

[lioneaglesolutions]

@jasontxf are you using Telescope?

I found this - laravel/telescope#289

[jasontxf]

oh wow! How did I miss such an important issue.
I didn't think Telescope could be the one causing it!

Thanks for sharing.

I am indeed using Telescope.
I'm going to try their solution one by one and see if any works for me.

1. Review Telescope Config File
2. Separate DB connection to another one
3. Disable Query Watcher

Today I will reviewed telescope config file and updated be the same as the latest version.
If it doesn't work I'll move to step 2 and eventually step 3.
Cross-finger one of the solutions will work!

@lioneaglesolutions have you tried any of the solution? Did it work?

[lioneaglesolutions]

Trying #3 first and then will probably go to number 2 anyway

[jasontxf]

Ok! Let's keep each other updated on what works :) Thanks!

[lioneaglesolutions]

So #3 did nothing - issue still occurring. Going to try a different Telescope connection

[jasontxf]

@lioneaglesolutions Just an update, my issue didn't seems to occur for the entire day.
Going to monitor for one whole day before I make any declaration :)