From ae74c921c3676cf0c31dbabcc462162a87ec73cf Mon Sep 17 00:00:00 2001 From: Terence Ma Date: Thu, 9 Nov 2023 16:23:05 +1100 Subject: [PATCH 1/4] init commit --- src/connections/destinations/actions.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index fc209ba99d..e2933a6ea3 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -201,3 +201,12 @@ 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 showed in Segment UI +Access Tokens that were generated from initial authorisation, e.g. when customer connects a destination via oauth, are always short-lived. Commonly, the token remains valid for 30 minutes to 1 hour.When Segment system receives 401 error responses from the destination afterwards, Segment will automatically make another request to the destion for a new token and retry the event which recived 401 error response. Therefore, when customers review the error response samples in our UI, the actual issue isn't always caused by the expired token. In addition, Segment has three event flows when events are received: + +1. through source +2. through event tester +3. 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. At the moment, we can't automatically refresh the tokens stored for the testers, thus, it is often expected that our customers need to manually re-authorize the destiantion again when they are sending events via our testers. From c78321088ab0e63d85474fc8a696e7ec7c31265f Mon Sep 17 00:00:00 2001 From: Terence Ma Date: Thu, 18 Jan 2024 16:14:49 +1100 Subject: [PATCH 2/4] update content --- src/connections/destinations/actions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index 5e0092b329..d5a7ad2d92 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -197,10 +197,10 @@ If no mappings are enabled to trigger on an event that has been received from th 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 showed in Segment UI -Access Tokens that were generated from initial authorisation, e.g. when customer connects a destination via oauth, are always short-lived. Commonly, the token remains valid for 30 minutes to 1 hour.When Segment system receives 401 error responses from the destination afterwards, Segment will automatically make another request to the destion for a new token and retry the event which recived 401 error response. Therefore, when customers review the error response samples in our UI, the actual issue isn't always caused by the expired token. In addition, Segment has three event flows when events are received: +Access Tokens that were generated from initial authorization, e.g. when customer connects a destination via Oauth, are always short-lived. Commonly, the token remains valid for 30 minutes to 1 hour.When Segment system receives 401 error responses from the destination afterwards, Segment will automatically make another request to the destion for a new token and retry the event which recived 401 error response. Therefore, when a 401 error response is received, the actual issue isn't always caused by the expired token. There are three event flows when events are received and sent to a destination: 1. through source 2. through event tester 3. 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. At the moment, we can't automatically refresh the tokens stored for the testers, thus, it is often expected that our customers need to manually re-authorize the destiantion again when they are sending events via our testers. +The underlying systems for these flows have their own copy of the token, which can expire at different points in time. From 6a8a612310b4745a386818ed9029327e6f5eab2c Mon Sep 17 00:00:00 2001 From: Terence Ma Date: Mon, 29 Jan 2024 12:10:14 +1100 Subject: [PATCH 3/4] update wording --- src/connections/destinations/actions.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index a1015aa196..bf3ab35d76 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -199,10 +199,11 @@ If no mappings are enabled to trigger on an event that has been received from th 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 showed in Segment UI -Access Tokens that were generated from initial authorization, e.g. when customer connects a destination via Oauth, are always short-lived. Commonly, the token remains valid for 30 minutes to 1 hour.When Segment system receives 401 error responses from the destination afterwards, Segment will automatically make another request to the destion for a new token and retry the event which recived 401 error response. Therefore, when a 401 error response is received, the actual issue isn't always caused by the expired token. There are three event flows when events are received and sent to a destination: +Access Tokens that were generated from initial authorization, e.g. when you connect a destination via Oauth, are always short-lived. Commonly, the token remains valid for 30 minutes to 1 hour. When Segment’s systems receive 401 error responses from the destination after a token has expired, Segment 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: 1. through source 2. through event tester 3. 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, and then one more request was made to actually send the data in your payload to the downstream destination. From b3a8c955dd5f7518e67b6f5809bab67f7c7ef8db Mon Sep 17 00:00:00 2001 From: Casie Oxford Date: Fri, 16 Feb 2024 10:38:03 -0600 Subject: [PATCH 4/4] Update actions.md grammar --- src/connections/destinations/actions.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index 792000e487..a2a97fe2f2 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -247,12 +247,12 @@ If no mappings are enabled to trigger on an event that has been received from th 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 showed in Segment UI -Access Tokens that were generated from initial authorization, e.g. when you connect a destination via Oauth, are always short-lived. Commonly, the token remains valid for 30 minutes to 1 hour. When Segment’s systems receive 401 error responses from the destination after a token has expired, Segment 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: +### 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: -1. through source -2. through event tester -3. through actions tester in mapping screen +- 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, and then one more request was made to actually send the data in your payload to the downstream destination. +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.