---
title: Events
url: https://www.tines.com/docs/events/
updated: 2026-02-19T19:47:59+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/llms.txt)*

# Events

*[View on tines.com](https://www.tines.com/docs/events/)*

## Introduction

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 calculation of key performance metrics.

> **TIP:**
> To learn more about how to reference event data, see our [Formulas docs](https://www.tines.com/docs/formulas/).
> 
> To learn more about how to loop through event data, see [Looping](https://www.tines.com/docs/actions/types/event-transformation/message-only/#looping).

## Event Structure

When an event is emitted by a Tines action, it will contain the result of the action and, if it exists, the received event. For example, the below image shows an event emitted by an action called "Type is infection". The "Type is infection" action is configured to receive events from an action called "Receive events":

![](https://www.datocms-assets.com/55802/1698947994-event_structure_image.png)

> **IMPORTANT:** The result of each action is contained in an object whose key is an underscored, lowercase form of the action's name (i.e., [snake cased](https://en.wikipedia.org/wiki/Snake_case)). For example: if the action's name is 'Send email', the result of the action will be contained in a key titled 'send\_email' in the emitted event.

## Re‑emit Events

It's possible to duplicate an existing event and pass it down to all receiving actions by selecting the event and clicking the **Re‑emit** button from the Action Events list. This can be used to repeatedly test the behaviour of a receiving action with the same data.

**Note**: There is a limit of 500 events that can be re-emitted at one time. 

![](https://www.datocms-assets.com/55802/1718626767-screenshot-2024-06-17-at-13-17-58.png)

## Daily Event Limits

> **NOTE:** Daily event limits **do not** apply to our [Community Edition](https://www.tines.com/get-started-with-tines-community-edition/) or [Starter Edition](https://www.tines.com/pricing/), both of which use monthly event limits. For more information, check out our edition comparison [here](https://explained.tines.com/en/articles/9620399-understanding-tines-pricing-and-packaging#h_4dce8c5280).

While Tines offers extremely generous event limits on all paid plans, there is a daily total event limit at the story and tenant level. When a story or tenant has reached 80 percent of its event limit, the owner of the story and the admins of the tenant will be notified via email. Tenant owners can also configure notifications to be sent at additional event usage percentages and to additional users and webhooks. If a story or tenant does reach its daily event limit, runs for the relevant story or tenant will be paused until the following day when the limit resets. 

This is extremely rare and most frequently occurs when there is an infinite loop executing. You can always reach out to a member of our team for help if you encounter this situation.

If you have version control enabled for your tenant, the story event limit is separate for the live and test version of the story.

Tenant owners can also configure daily event limits for individual teams. Read more about this in the [event limit settings](https://www.tines.com/docs/event-limit-alerts/) documentation.