When an action runs, it completes its job and passes data to the next action in your workflow in what we call an event.

Each time an action executes and emits an event, it counts toward your event limit for your story/tenant. Event limits are measured daily or monthly depending on your plan. You can learn more about this here.

The number of events emitted by a particular action is shown in a pill in the top right of each action. For example, here we see that each action in this story for sending daily jokes in an email have 3 emitted events making a total of 12 events in the story.

Under the events tab you'll be able to delete or re-emit events, as well as view the details of each event:

Events emitted from all actions upstream will be contained in the receiving action. There is a 100MB limit on the size of an event. For more details on events see here.

By default, Tines retains event and log data for seven days. Depending on your Tines subscription, you can configure how long event and log data are stored in Tines. Open your story, and on the right panel, select the desired option from "Keep events and logs."

Then select how long you would like to store the data for:

If the period of retention has passed, the events cannot be recovered.

Events represent the structured data sent between actions. Events are JSON objects making them flexible and easy to read. All events are timestamped and "write-once", providing an audit trail and making them an ideal basis for the calculation of key performance metrics.

Below are the limits on the number of events you can have in your Tines tenant.

Read how usage in Tines is calculated here.