You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 14, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/features/logs.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,19 +56,19 @@ Call Specific Sub-Events:
56
56
57
57
## Custom Queries
58
58
59
-
Besides the predefined filters on the logs table, you can use any custom queries to dig deep. For example: `$.request.mergeTags.firstName="Jane"`
59
+
Besides the predefined filters on the logs table, you can use any custom queries to dig deep. For example: `$.request.parameters.firstName="Jane"`
60
60
61
61
You can search for anything in the `$.request`, which contains the [original parameters you passed to send()](/reference/server.md#send). Here's an example of a `$.request` object:
@@ -181,14 +181,14 @@ Yes, with the `trackingId`, you can cancel a scheduled notification before it is
181
181
182
182
### How is error checking and logical operations handled with scheduled notifications?
183
183
184
-
Every notification request is evaluated for correct notificationId, being below the usage quota, valid user preferences, and more. For scheduled notifications, these checks are done twice:
184
+
Every notification request is evaluated for correct type, being below the usage quota, valid user preferences, and more. For scheduled notifications, these checks are done twice:
185
185
186
186
1. Once at the time of receiving the initial request, similar to regular notifications. The results of this step can be found in the response body of your request and in our [log dashboard](logs.md).
187
187
2. Once again at the scheduled time. The results of this step can also be found in our [log dashboard](logs.md).
188
188
189
189
The only exceptions are throttling and deduplication checks that only happen at the scheduled time.
190
190
191
-
So for example, an invalid `notificationId` error might be generated initially if the notificationId is incorrect, or later if the notification is deleted.
191
+
So for example, an invalid `type` error might be generated initially if the type is incorrect, or later if the notification is deleted.
192
192
193
193
### How are logics managed for scheduled notifications?
0 commit comments