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

Skip to content

Add note on delivery overview if no mapping for event #5311

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 2 commits into from
Sep 26, 2023
Merged

Add note on delivery overview if no mapping for event #5311

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
452e226
Add note on delivery overview if no mapping for event
bobbyatsegment Sep 7, 2023
589263a
Small fix
rchinn1 Sep 26, 2023
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
3 changes: 3 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 @@ -193,6 +193,9 @@ When you send an event with an actions destination Event Tester that doesn't mat

If no mappings are enabled to trigger on an event that has been received from the connected source, the destination will not send any events. Ensure that at least one mapping has been configured and enabled in the destination mappings for an event that you would like to reach downstream.

> info ""
> Events without mappings enabled to handle them display as being discarded due to "No matching mapping" in a destination's Delivery Overview.

### 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.