Skip to content

Commit 41dc321

Browse files
chrisosanscontext
andauthored
Update src/connections/functions/destination-functions.md
Co-authored-by: LRubin <[email protected]>
1 parent e843c1a commit 41dc321

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/functions/destination-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ To change which type of event the handler listens to, you can rename it to the n
8686

8787
A function's execution is considered successful if it finishes without any errors. You can also `throw` an error to indicate a failure on purpose. You can use these errors to validate event data before processing it, to ensure your function works as expected.
8888

89-
There are four pre-defined error types that you can `throw` to indicate that the function ran as expected, but that data could not be delivered:
89+
You can `throw` the following pre-defined error types to indicate that the function ran as expected, but that data could not be delivered:
9090

9191
- `EventNotSupported`
9292
- `InvalidEventPayload`

0 commit comments

Comments
 (0)