Effectively managing your event limits in Tines is crucial for ensuring the smooth and continuous operation of your intelligent workflows. By proactively configuring limits and setting up timely alerts, you can prevent a single active team or runaway story from consuming your overall tenant capacity.
This article will give you a refresher on what an event is and what the event limits are for each plan in Tines.
Here are the best practices for managing your tenant event limits:
Allocating limits to teams
A best practice for tenant owners is to strategically allocate event limits to individual teams.
Prioritize active teams
Allocate a higher number of events to your most active teams. This prevents one busy team from exhausting the overall tenant limit and impacting other teams.
For example, a tenant owner can assign 15,000 events to the security team from the 20,000 total tenant-wide limit.
Note: While stories within your Personal team do not count towards licensing (as they cannot be published), they do count toward your overall tenant-wide event limits.
Tenant health
You can utilize the tenant health page in Tines to identify which stories and teams to prioritize. The tenant health page includes a "Most active stories" graph that you can see in the below image along with a list of the most active stories (via action runs) and their associated team for a given timeframe (default: 7 days).
You can use this information when allocating team event limits, especially in longer-standing tenants where your teams' needs change.
Configuring timely notifications
Timely alerts are essential for staying ahead of your event usage. Automated notifications are sent to story owners and tenant owners once usage reaches 80% and 100% of the daily limit by default. Tenant owners can manage event limit settings for tenant-wide, team, and global story thresholds.
Set custom thresholds
Utilize custom notification thresholds to receive alerts before reaching critical limits. You can set notifications to trigger when an event limit from 40% is reached.
Choose your notification method
Alerts for event thresholds can be delivered via two primary methods:
Email: Send notifications via email to configured recipients.
Webhook action: Route notifications through a webhook action to external platforms such as Slack, Microsoft Teams, or Jira. This method allows you to build a story that sends alerts from the webhook action to a specific channel or automatically opens a ticket when limits are approached.
Notification recipients
When managing event limits, you can specify who receives notifications for threshold alerts, this includes both users and webhooks. You can also specify which team's limits they should be notified about.
For example, a team admin for the security team can be configured to receive alerts specifically for that team's limits, without having visibility into the tenant-wide limits.
Increasing your event limits
If your tenant is consistently hitting its maximum daily event limit, you will need to discuss an increase with your account owner.
Note: Tenant wide and global story event limits are configurable on self-hosted tenants.
Read more on event limit settings in our docs here.