docs: add troubleshooting for subscribers + scheduled jobs not working (#13762)
This commit is contained in:
1 parent
ee1c77a01f
commit
4eb9628514
13 files changed
+308
-13
No files matched your search
@@ -94,6 +94,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](!resources!/troubleshooting/subscribers/not-working).
|
||||
|
||||
---
|
||||
|
||||
## Event Module
|
||||
|
||||
@@ -79,6 +79,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](!resources!/troubleshooting/scheduled-job-not-running).
|
||||
|
||||
---
|
||||
|
||||
## Example: Sync Products Once a Day
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
export const generatedEditDates = {
|
||||
"app/learn/fundamentals/scheduled-jobs/page.mdx": "2025-07-25T15:56:17.926Z",
|
||||
"app/learn/fundamentals/scheduled-jobs/page.mdx": "2025-10-16T09:35:54.393Z",
|
||||
"app/learn/fundamentals/workflows/page.mdx": "2024-12-09T14:45:17.837Z",
|
||||
"app/learn/deployment/page.mdx": "2025-09-29T10:25:29.915Z",
|
||||
"app/learn/page.mdx": "2025-06-27T11:39:15.941Z",
|
||||
@@ -15,7 +15,7 @@ export const generatedEditDates = {
|
||||
"app/learn/fundamentals/medusa-container/page.mdx": "2025-07-25T13:18:36.859Z",
|
||||
"app/learn/fundamentals/api-routes/page.mdx": "2025-07-25T15:19:33.365Z",
|
||||
"app/learn/fundamentals/modules/modules-directory-structure/page.mdx": "2025-07-25T15:40:20.362Z",
|
||||
"app/learn/fundamentals/events-and-subscribers/page.mdx": "2025-05-16T13:40:16.111Z",
|
||||
"app/learn/fundamentals/events-and-subscribers/page.mdx": "2025-10-16T09:36:04.864Z",
|
||||
"app/learn/fundamentals/modules/container/page.mdx": "2025-07-31T14:24:04.087Z",
|
||||
"app/learn/fundamentals/workflows/execute-another-workflow/page.mdx": "2025-08-01T07:28:51.036Z",
|
||||
"app/learn/fundamentals/modules/loaders/page.mdx": "2025-06-16T13:34:16.462Z",
|
||||
|
||||
@@ -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