docs: add troubleshooting for subscribers + scheduled jobs not working (#13762)
This commit is contained in:
@@ -12038,6 +12038,10 @@ Sending confirmation email...
|
||||
|
||||
The first message indicates that the `order.placed` event was emitted, and the second one is the message logged from the subscriber.
|
||||
|
||||
### Troubleshooting Subscribers
|
||||
|
||||
If your subscriber is not working as expected, refer to the [Subscriber Troubleshooting Guide](https://docs.medusajs.com/resources/troubleshooting/subscribers/not-working/index.html.md).
|
||||
|
||||
***
|
||||
|
||||
## Event Module
|
||||
@@ -15406,7 +15410,7 @@ In this case, the relation would always be one-to-many, even if only one post is
|
||||
|
||||
Whether you're using a one-to-one or one-to-many relation for an inverse read-only module link, the relation name is always the alias of the second data model. It's not changed to its plural form for one-to-many relations.
|
||||
|
||||
For example, looking again at the the forced one-to-many relation example:
|
||||
For example, looking again at the forced one-to-many relation example:
|
||||
|
||||
```ts
|
||||
import BlogModule from "../modules/blog"
|
||||
@@ -18509,6 +18513,10 @@ After a minute, the following message will be logged to the terminal:
|
||||
info: Greeting!
|
||||
```
|
||||
|
||||
### Troubleshooting Scheduled Jobs
|
||||
|
||||
If your scheduled job is not running at the expected times, refer to the [Scheduled Job Troubleshooting Guide](https://docs.medusajs.com/resources/troubleshooting/scheduled-job-not-running/index.html.md).
|
||||
|
||||
***
|
||||
|
||||
## Example: Sync Products Once a Day
|
||||
|
||||
Reference in New Issue
Block a user