@@ -250,16 +250,17 @@ To resume sending notifications, execute
250
250
If notifications are not being delivered, use the following methods to
251
251
troubleshoot:
252
252
253
- 1 . Ensure notifications are being added to the ` notification_messages ` table
254
- 2 . Review any error messages in the ` status_reason ` column, should an error
255
- have occurred
256
- 3 . Review the logs (search for the term ` notifications ` ) for diagnostic
257
- information< br > _ If you do not see any relevant logs, set
258
- ` CODER_VERBOSE=true ` or ` --verbose ` to output debug logs _
259
- 4 . If you are on version 2.15.x, notifications must be enabled using the
253
+ 1 . Ensure notifications are being added to the ` notification_messages ` table.
254
+ 1 . Review any available error messages in the ` status_reason ` column
255
+ 1 . Review the logs. Search for the term ` notifications ` for diagnostic information.
256
+
257
+ - If you do not see any relevant logs, set
258
+ ` CODER_VERBOSE=true ` or ` --verbose ` to output debug logs.
259
+ 1 . If you are on version 2.15.x, notifications must be enabled using the
260
260
` notifications `
261
- [ experiment] ( https://coder.com/docs/contributing/feature-stages#experimental-features ) .
262
- Notifications are enabled by default starting in v2.16.0.
261
+ [ experiment] ( ../../../contributing/feature-stages.md#experimental-features ) .
262
+
263
+ Notifications are enabled by default in Coder v2.16.0 and later.
263
264
264
265
## Internals
265
266
@@ -270,7 +271,7 @@ concurrency.
270
271
271
272
All messages are stored in the ` notification_messages ` table.
272
273
273
- Messages older than 7 days are deleted.
274
+ Messages older than seven days are deleted.
274
275
275
276
### Message States
276
277
0 commit comments