Skip to content

Commit 54d6905

Browse files
committed
Adding the Event Status grid to the troubleshooting page
1 parent 17dfb9b commit 54d6905

File tree

2 files changed

+11
-7
lines changed

2 files changed

+11
-7
lines changed
139 KB
Loading

src/pages/events/troubleshooting.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,15 @@ You can use the following SQL query to select all events from the `event_data` t
2626

2727
`SELECT * FROM event_data`
2828

29-
Use the query results to determine the next troubleshooting step.
29+
Alternatively, the _Event Status_ grid, found by navigating to **System** > Events > **Event Status** in the Commerce admin, provides a way to view the status of triggered events contained in the `event_data` table through the UI.
3030

31-
### The table is empty
31+
![Event Status grid](../_images/events/event-status-grid.png)
3232

33-
If the `event_data` table is empty, use the following procedure to diagnose the problem:
33+
Use the SQL query results or the content of the _Event Status_ grid to determine the next troubleshooting step.
34+
35+
### The table or grid is empty
36+
37+
If the `event_data` table or the _Event Status_ grid is empty, use the following procedure to diagnose the problem:
3438

3539
1. Run `bin/magento events:list` to ensure that you have subscribed events.
3640

@@ -48,14 +52,14 @@ If the `event_data` table is empty, use the following procedure to diagnose the
4852
ENABLE_EVENTING: true
4953
```
5054
51-
### The event status is `0`
55+
### The event status is `0` or `Waiting`
5256

53-
Events are sent by crons. If the status of an event in the `event_data` is still `0` after a long period, then the crons are not configured correctly.
57+
Events are sent by crons. If the status of an event is still `0` in the `event_data` table or `Waiting` in the _Event Status_ grid after a long period, then the crons are not configured correctly.
5458
In a Cloud environment, check the logs. Cron execution might have been killed due to lack of space in the environment or other reasons.
5559

56-
### The event status is `2`
60+
### The event status is `2` or `Failure`
5761

58-
The event status `2` indicates there was an error during transmission. Additional information can be found in the `info` column of the table or in the `system.log` file.
62+
An event status of `2` in the `event_data` table, or `Failure` in the _Event Status_ grid, indicates there was an error during transmission. Additional information can be found in the `info` column of the table or in the `system.log` file.
5963
The following CLI command can show only logs related to the event batch sending.
6064

6165
```bash

0 commit comments

Comments
 (0)