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
Subscriber is not stable #7156
Comments
Quick question but are you using |
@adevinwild yes. I'm using Redis in local and prod |
We are facing the same issue while trying order placed subscriber. We tested redis on local, railway and redis website. However same problem. In our case medusa prod deployment on railway often fails to trigger the subscribers whereas local deployment of medusa generally works (not always). Attaching the log when it doesn't trigger the subscriber. There is no error and no mention of the order.placed subscriber. When it works successfully I get the following logs
Updating all the package versions helped. Earlier prod was not working at all when event-bus-redis is enabled. It was only working 60-70% of the time with event-bus-local. Here is current dependencies in my package.json
Please share any thoughts on fixing this. Currently our migration to medusa is blocked on this. Thank you, |
Forgot to mention. |
Describe the bug
Sometimes subscriber does not work.
I create a subscriber:
It works at first, but after some time, it stops working.
This issue occurs not only on my local machine but also on the production server (docker + k8s).
To resolve the issue, I need to delete the node_modules folder and then reinstall everything.
System information
Medusa version (including plugins): 1.20.4
Node.js version:
v18.17.1
Database: pgsql 16.2
Operating system: Ubuntu 20.04
Browser (if relevant):
Steps to reproduce the behavior
It is hard to reproduce. Sometimes it happens.
Expected behavior
Subscriber must work stably.
The text was updated successfully, but these errors were encountered: