-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Bug]: Subscriber is not working #10848
Comments
Hi, The subscribers are loaded but It does not catch I did other tests with I do not know if these concern the same bug. Thanks for your helps. |
Same issue most of events are not captured, v2.2. I have even recreated the workflow locally and tried emitting events manually and they still not working. I tried with fulfillment.created |
Same issue here with v2.2, with the event-bus-redis, events are being added to Redis, but no operation or logs are shown. I tried with product.created, product.updated, order.placed |
Is it a redis provider issue? I havent tested with local, will try. For the full process from creating a cart and placing an order, only SomehtingLink.attached and order.placed events are occured only. Nor cart.created, cart.updated, paymnent_collection.created/initiated (or how it is called) |
@maselious I figured it out by removing Its mentioned here: https://docs.medusajs.com/v1/development/worker-mode Anyone who is deploying only one instance of Medusa needs to set it to |
It worked partially for me in the workmode = shared or server.
Best regards,
NT
Le lun. 13 janv. 2025, 20:21, Muhammad Umar ***@***.***> a
écrit :
… @maselious <https://github.com/maselious> I figured it out by removing
workerMode from my medusa-config.ts file. It was set to server. I
suppose, when workerMode is server that "worker" wont process any
subscribers. Works now on both local and production (using Railway)
—
Reply to this email directly, view it on GitHub
<#10848 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFSDBL5Q6IPIGLDWVZ6GLJL2KQG3XAVCNFSM6AAAAABUWXSMASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBXHE4TSMJRGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thank you for adjusting it to "shared" then it worked, but it still doesn't function with "server." Nevertheless, it's a step forward. |
Package.json file
Node.js version
v20.17.0
Database and its version
16.2
Operating system name and version
macos sonoma Version 14.5 (23F79)
Browser name
Chrome
What happended?
Hello development team, I am currently having an issue with the subscriber. It is no longer working, and I don't know the cause. This has become necessary when resetting the password for customers who need the subscriber to get the token. Please respond to me.
Expected behavior
When starting up, it usually loads the events in the src/subscriber directory. Currently, I need to use it to generate a password reset token.
Actual behavior
Contrary to expectations, the subscriber could not be loaded and this caused it to not function.
Link to reproduction repo
https://github.com/Buudc99/medusa-subscriber-not-working.git
The text was updated successfully, but these errors were encountered: