Automations Reference
Reference for Automation availability, quotas, triggers, statuses, notifications, billing, and workspace checks.
Availability and limits
| Plan | Access | Shared workspace definition limit |
|---|---|---|
| Free | No | 0 |
| Lite | No | 0 |
| Pro | Yes | 10 |
| Elite | Yes | 50 |
Draft, active, and paused definitions count toward the limit. Archived definitions do not. Definitions are owner-private even in an Elite organization.
Definition fields
| Field | Constraint or value |
|---|---|
| Name | Required, up to 100 characters. |
| Instructions | Required, up to 8,000 characters. |
| Operation | agent_y2 |
| Overlap policy | skip_if_running |
| Status | Draft, active, paused, or archived. |
| Notification policy | All runs, failures only, or none. |
| Project | Optional active Project with the same owner and workspace. |
Schedule triggers
| Frequency | Required fields |
|---|---|
| Daily | Time of day and IANA timezone. |
| Weekly | Time of day, timezone, and weekday. |
| Monthly | Time of day, timezone, and day of month. |
Run states
queued → running → succeeded or failed is the normal path. A run can instead become
skipped when admission checks fail or another run overlaps, or canceled when its work is
explicitly stopped.
Billing states are reserved, settled, released, and none. A released state means the
request hold was returned without creating settled usage. Each run snapshots the
definition revision, instruction, name, trigger, workspace, optional Project, and cost metadata.
Live admission checks
Before paid work starts, Y2 verifies:
- The definition is active and still at the queued revision.
- The owner is still a member of the definition workspace.
- The workspace still has Pro or Elite Automation access and Chat capacity.
- A bound Project is active, owner-matched, workspace-matched, and entitled.
- No earlier run for the definition is currently active.
These checks apply to schedules, report events, manual runs, and workflow continuation.