Overview
While building out and running stories in Tines, especially with send to story actions, you might run into the following error on your sub-stories:
Could not find a matching action to return event. If this action ran because of a Send to Story event, ensure that the original event contained #agent_id and #event_id keys.
This article covers common causes and solutions to the behavior.
Cause and Solution
Cause One: Independent action run
An action within a send to story flow was run independently, outside of the send to story flow (i.e. manually running an action).
🟢 Solution: If this occurred because you ran an action manually, you'll want to re-emit the last event from the upstream webhook "entry" action in the story instead.
Cause Two: Page action outside of the send to story flow
There is a page action in the sub-story as another input/entry. When the page action emits an event, this error will show in the exit action of the sub-story, as the flow happened outside of the send to story flow.
🟢 Solution: Include page actions within your send to story flow.
Cause Three: Non-send to story event source
A story is set up for a send to story flow, and a request comes into a webhook (configured as an "entry" action) from a source other than a send to story action.
🟢 Solution: If you are not using a story in a send to story flow, make sure to turn off the Send to Story setting within the story configuration panel.
Need further assistance?
Have questions or still seeing the error after working through the sections above? We are happy to help!
⬇️ Contact Tines Support with the information below, when available:
ℹ️ General Information:
Describe the behavior in detail, including steps to replicate (we recommend providing this information via a screen recording).
The time and date of the reported behavior.
ℹ️ Story Details:
Impacted Story's URL (include all URLs if there are multiple stories impacted).
Impacted Action's ID (include all IDs if there are multiple actions impacted).
Relevant action event data. You can find this via the event panel.
The action configuration(s):
You can copy + paste actions into a code block; this will provide the configuration of the action(s) in a JSON format so that Tines Support can use it into our test environments.