Limits & Permissions
Plans, roles and the scheduled quota that broadcasts share with scheduled triggers
Three things control who can use broadcasts: your plan, your role and a shared quota of scheduled work.
Plans
| Plan | Broadcasts |
|---|---|
| Free | Not available. The page shows an upgrade card. |
| Standard | Not available. The page shows an upgrade card. |
| Pro | Available. Up to 25 active broadcasts and scheduled triggers combined. |
| Enterprise | Available. No cap. |
On Free or Standard the page shows an upgrade card with a Pro feature label and the buttons Upgrade to Pro and Compare plans. The sidebar link stays visible so you can find the feature.
If you downgrade to a plan without broadcasts, Wexio does not send the ones still scheduled. They end as Failed with a tooltip on the badge. See Lifecycle & Cancellation.
Roles
| Role | See broadcasts | Create, edit, cancel, retry |
|---|---|---|
| Owner | Yes | Yes |
| Admin | Yes | Yes |
| Editor | Yes | Yes |
| Agent | Yes | No |
Agents see the list, the details and the history. The Add schedule button shows a tooltip, You don't have permission to manage broadcasts, and the edit, cancel and retry buttons are hidden. The API refuses the same actions.
Combined Quota
Broadcasts and scheduled triggers share one cap on Pro. Without a shared cap, an organisation could queue 25 of each.
What Counts
| Item | Counts toward the cap |
|---|---|
| A broadcast with status Scheduled | Yes |
| A broadcast that is Sending, Completed, Cancelled or Failed | No |
| A scheduled trigger that is relative to a contact date | Yes |
| A scheduled trigger that repeats on a cron schedule | Yes |
| A one-off scheduled trigger with a time in the future | Yes |
| A one-off scheduled trigger with a time in the past | No |
| A scheduled trigger that is not set up yet | No |
A scheduled trigger counts while its flow is still a draft, so you find out at setup and not when you publish.
When You Reach the Cap
The Add schedule button is disabled with the message You've reached the limit of 25 active broadcasts. A scheduled trigger can't be added to a flow either.
To free a slot, cancel a scheduled broadcast or delete a scheduled trigger. A broadcast stops counting once it starts sending.
A retry creates a new broadcast, so it counts toward the cap like any other.
Ops
Broadcasts use your plan's ops. Each delivered send costs 1 op. If you run out and usage credits are off, the remaining sends fail with ops_limit_reached. See Ops Usage.
Other Limits
| Limit | Value |
|---|---|
| Minimum time before a send | 2 minutes |
| Late-send window | 5 minutes. After that the broadcast ends as Failed. |
| Name length | 200 characters |
| Live activity log | Kept for 30 days |
| Audience size | No cap |
| Sending speed | Set by the channels, not by you. See Delivery & Logs. |
Related
- Scheduling: the 2 minute and 5 minute rules.
- Scheduled Trigger: the other half of the shared quota.
- Lifecycle & Cancellation: cancel a broadcast to free a slot.