Destination Functions: Document error types #677
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tysonmote
requested review from
benhorowitz,
danielstjules and
n2parko
as code owners
sanscontext
reviewed
Mar 3, 2020
| ### Errors That Are Retried | ||
|
|
||
| * "Internal": An error not thrown by your function code and not covered by any other error classification. This is most commonly caused by your function exceeding its time limit, which is 5 seconds by default. | ||
| * "Too Many Requests": Your Function is receiving too many events and is being throttled. If this error persists for more than an hour, please email us at [friends@segment.com](mailto:friends@segment.com) for help. |
There was a problem hiding this comment.
We no longer give out this email alias in docs.
sanscontext
suggested changes
Mar 3, 2020
|
Some style notes:
|
Co-Authored-By: LRubin <sanscontext@users.noreply.github.com>
Co-Authored-By: LRubin <sanscontext@users.noreply.github.com>
Co-Authored-By: LRubin <sanscontext@users.noreply.github.com>
|
@sanscontext Thanks! I think I may have looked at an old page to determine if we used titlecase or not. That's now fixed (I think). |
|
I don't think we've been consistent in the past, so no worries either way. Destination Function is still a product name technically and doesn't need to be decapped, but this is close enough. :) |
sanscontext
approved these changes
Mar 3, 2020
|
Oh hey! is this at all useful to link to and from? https://segment.com/docs/connections/integration_error_codes/ |
|
Those codes don't quite apply to Destination Functions. Thanks for the heads-up though! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Destination Functions can return errors that are visible in Event Delivery but their meaning isn't clear (yet). I added documentation to clear that up.
Related issues (optional)
Fixes FUN-619: https://segment.atlassian.net/browse/FUN-619