Closed HpiGuillaume closed 5 years ago
This has to do with Job Auto Tenancy we implemented in the dev branch. Provided possible solutions/things to think of through Discord, will be tested by @HpiGuillaume .
@HpiGuillaume Can this be closed, did we provide you with enough information or is more info still needed?
@ArlonAntonius sorry to not have tested since 6 days but I don't have time :/
I use only the system
database now for my jobs so it's not blocking me. I prefer fix more blocking issue in my prod :)
I think it's bug, or just a mistake in my configuration files. I close with this message, but re-open when I've taking time to test the possible solution !
Description
When I've use the Queue management of Laravel v5.7.26 with Tenancy 5.x-dev, all new jobs were inserted in the jobs system table instead of jobs tenant table.
Information
I want queue on each tenant and, in plus, one for system. Purpose of those queue, manage mail.
Code I've use to insert in job:
The job class:
By asking some help in the Discuss chat, @Plytas asking me to print the current tenant in
handle
method, and there was the good tenant displayed.In the record in job table on system database, I've a "tenant_id:9" in the
playload
field (that are the good one too).So don't understand why the record don't going into the good database.
tenancy.php config
queue.php config