Skip to content

Commit 266f983

Browse files
Update src/connections/destinations/actions.md
Co-authored-by: forstisabella <[email protected]>
1 parent f997808 commit 266f983

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/destinations/actions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -329,7 +329,7 @@ When an event triggers multiple mappings, a request is generated for each mappin
329329
#### Why is an OAuth "access token expired" message appearing in Segment?
330330
Access tokens generated during initial authorization are short-lived, for example, when you connect a destination via OAuth. The token typically remains valid for 30 minutes to 1 hour. When Segment receives a `401 error` response from a destination after a token expires, it will automatically request 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 3 event flows when events are received and sent to a destination:
331331

332-
- through source.
332+
- Through a source
333333
- through event tester.
334334
- through actions tester in mapping screen.
335335

0 commit comments

Comments
 (0)