Skip to content

Commit 27672dc

Browse files
committed
Correct Events Status name
1 parent 54d6905 commit 27672dc

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/pages/events/troubleshooting.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -26,15 +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-
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.
29+
Alternatively, the _Events Status_ grid, found by navigating to **System** > Events > **Events 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-
![Event Status grid](../_images/events/event-status-grid.png)
31+
![Events Status grid](../_images/events/event-status-grid.png)
3232

33-
Use the SQL query results or the content of the _Event Status_ grid to determine the next troubleshooting step.
33+
Use the SQL query results or the content of the _Events Status_ grid to determine the next troubleshooting step.
3434

3535
### The table or grid is empty
3636

37-
If the `event_data` table or the _Event Status_ grid is empty, use the following procedure to diagnose the problem:
37+
If the `event_data` table or the _Events Status_ grid is empty, use the following procedure to diagnose the problem:
3838

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

@@ -54,12 +54,12 @@ If the `event_data` table or the _Event Status_ grid is empty, use the following
5454
5555
### The event status is `0` or `Waiting`
5656

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.
57+
Events are sent by crons. If the status of an event is still `0` in the `event_data` table or `Waiting` in the _Events Status_ grid after a long period, then the crons are not configured correctly.
5858
In a Cloud environment, check the logs. Cron execution might have been killed due to lack of space in the environment or other reasons.
5959

6060
### The event status is `2` or `Failure`
6161

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.
62+
An event status of `2` in the `event_data` table, or `Failure` in the _Events 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.
6363
The following CLI command can show only logs related to the event batch sending.
6464

6565
```bash

0 commit comments

Comments
 (0)