Thanks to visit codestin.com
Credit goes to github.com

Skip to content

add oauth faq for actions destination #5656

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Feb 16, 2024
Merged

add oauth faq for actions destination #5656

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
ae74c92
init commit
terence1988 Nov 9, 2023
1f1f4aa
Merge branch 'develop' into add-oauth-faq-for-actions-destination
terence1988 Jan 18, 2024
c783210
update content
terence1988 Jan 18, 2024
9d47c62
Merge branch 'develop' into add-oauth-faq-for-actions-destination
terence1988 Jan 29, 2024
6a8a612
update wording
terence1988 Jan 29, 2024
4cd76e2
Merge branch 'develop' into add-oauth-faq-for-actions-destination
terence1988 Feb 8, 2024
b3a8c95
Update actions.md
cmastr Feb 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/connections/destinations/actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -246,3 +246,13 @@ If no mappings are enabled to trigger on an event that has been received from th
### Multiple mappings triggered by the same event

When the same event triggers multiple mappings, a request will be generated for each mapping that's configured to trigger on an event. For example, for the *Subscription Updated* event, if two mappings are enabled and both have conditions defined to trigger on the *Subscription Updated* event, the two requests will be generated and sent to the destination for each *Subscription Updated* event.

### Oauth "access token expired" message shown in Segment UI
Access Tokens that were generated from initial authorization, for example, when you connect a destination via Oauth, are always short-lived. Commonly, the token remains valid for 30 minutes to 1 hour. When Segment receives 401 error responses from the destination after a token has expired, it will automatically make another request to the destination for a new token and will then retry the event. Therefore, 401 responses are sometimes expected and do not indicate an event failure. There are three event flows when events are received and sent to a destination:

- through source
- through event tester
- through actions tester in mapping screen

The underlying systems for these flows have their own copy of the token, which can expire at different points in time.
Threfore, if you see a 401 error in a sample response, it is likely that you’ll also see another request was made after it, to ask the downstream destination for a new token. Then one more request was made to actually send the data in your payload to the downstream destination.