You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a queued listener is triggered on a secondary queue, it is also showing within pulse as queued on default as well. The secondary queue jobs process perfectly and show as the purple processed line, however the line remains in the default queue. Horizon shows all outstanding jobs completed. Looking at the database pulse_aggregates table I see the duplicate records being created despite the technical processing working as expected.
Steps To Reproduce
Triggered a queued listener on a secondary queue to default using the ShouldQueue implementation. Define the queue within the listener itself (public $queue = 'secondary_queue';)
Pulse shows both the secondary queue and default queue graphs both with a spike displaying queued jobs, whereas should only show in the secondary.
The text was updated successfully, but these errors were encountered:
Winger15mk
changed the title
Queued listener on secondary queue is also being displayed on the default queue
Queued listener on secondary queue is also being displayed on the default queue graph under 'Queues' card
Feb 1, 2024
Pulse Version
1.0.0-beta11
Laravel Version
10.43.0
PHP Version
8.2
Livewire Version
3.2.0
Database Driver & Version
No response
Description
When a queued listener is triggered on a secondary queue, it is also showing within pulse as queued on default as well. The secondary queue jobs process perfectly and show as the purple processed line, however the line remains in the default queue. Horizon shows all outstanding jobs completed. Looking at the database pulse_aggregates table I see the duplicate records being created despite the technical processing working as expected.
Steps To Reproduce
The text was updated successfully, but these errors were encountered: