Skip to content

Commit 9b37530

Browse files
Update actions.md
1 parent 7549c55 commit 9b37530

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

src/connections/destinations/actions.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -168,3 +168,13 @@ You can combine criteria in a single group using **ALL** or **ANY**. Use an ANY
168168
> - You need to filter data from multiple types of call (for example, Track, Page, and Identify calls)
169169
>
170170
> If your use case does not match these criteria, you might benefit from using Mapping-level Triggers to match only certain events.
171+
172+
## FAQ & Troubleshooting
173+
174+
### Validation error when using the Event Tester
175+
176+
A validation error with the description "You may not have any subscriptions that match this event" will surface when sending an event with an Actions destination's event tester that does not match the trigger of any configured and enabled mappings. To resolve this, either a mapping must be created with a trigger to handle the event being tested, or the test event's payload must be updated to match the trigger of any existing mappings.
177+
178+
### Multiple mappings triggered by the same event
179+
180+
A request will be generated for each mapping that's configured to trigger on an event. For example, with an event named "Subscription Updated", if two mappings are enabled and both have conditions defined to trigger on "Subscription Updated" events, two requests will be generated and sent to the destination for each "Subscription Updated" event.

0 commit comments

Comments
 (0)