-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Email sending is frozen #216
Comments
I am facing this issue also but my campaign stuck on 60 emails.. my que connection is sync and cron job runs every 30mints is it ok |
Same through Amazon SES, any idea ? |
@art-n |
Hey @umerghori786, Thank you for the reply. I've edited .env file, but I miss with "your db should have jobs table". I only have an empty "failed jobs" table. So I've tried to run php artisan but nothing happens. |
php artisan queue:table this command make job table..... i think you first delete failed jobs table also before running this command then its works... you can ask me if you face any issue |
@art-n after job table
|
Thank you for your help @umerghori786 I now have jobs table. But for any reasons it changes sending to sent status but no more emails has been sent. I also tried to change sent status to queued and fire php artisan command, same result. |
php artisan schedule:run do you run this command ? bcz this command responsible to send emails in jobs table |
In order to use the database queue driver, you will need a database table to hold the jobs. To generate a migration that creates this table, run the queue:table Artisan command. Once the migration has been created, you may migrate your database using the migrate command:
Finally, don't forget to instruct your application to use the database driver by updating the QUEUE_CONNECTION variable in your application's .env file: |
As you can see from the screenshot, sending the e-mail stopped in this way. It's been this way for about 24 hours. I am using Amazon SES.
There are no errors in the log record.
Thank you for your help.
The text was updated successfully, but these errors were encountered: