Skip to content
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

Optimize the process notifications scheduled task #316

Closed
GshopMaxime opened this issue Nov 21, 2022 · 2 comments
Closed

Optimize the process notifications scheduled task #316

GshopMaxime opened this issue Nov 21, 2022 · 2 comments

Comments

@GshopMaxime
Copy link

Describe the bug
When a scheduled task in Shopware fails, the task status is updated accordingly, but the scheduled task is never restarted.
In a production environment this means that the process notifications task suddenly stops updating payment statuses.
Our client has to notify us and we have to manually edit the task status in the database. The whole automated logistics process is tied to the payment status, which means precious time is lost.

Versions
Shopware version: 6.4.15.1
Plugin version: 3.7.0

Possible solutions
-Quick and dirty:
Add a second scheduled task that is responsible for restarting the first if it fails.

-Optimal:
Use the message worker to process the notifications one by one. When one of the notifications fails, this won't affect the scheduled tasks status. Furthermore a failed message is automatically retried.

@peterojo
Copy link
Contributor

peterojo commented Mar 6, 2023

Hi @GshopMaxime, apologies for the late response,
we have released an update with the option to reschedule unprocessed payment methods in the admin.
We also added a new console command to trigger a reprocessing of expired tasks that were not yet processed.
This will help to mitigate the issue if there is a server failure on the merchants side that leads to a failure of the scheduled tasks. Please checkout the release notes for 3.7.0 for more info

@peterojo
Copy link
Contributor

Closing this issue for lack of activity. Assuming the aforementioned released solved this issue.
Please feel free to reopen if new details of the same issue emerge, or create a new report if there is a different issue.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants