Checking Asana limits on storage, history and automation

Asana Personal lists unlimited storage, with a 100 MB maximum per file; Starter includes Personal's storage terms. Starter also lists unlimited automations, and a 2024 Asana Community update says the former limit of 250 rule actions a month no longer applies. Asana Pricing gives no history-retention period, while a 2020 community post reports that some repeated task changes may appear only as their latest update.

Define each requirement

Asana Pricing lists unlimited storage and a 100 MB maximum per file for Personal. Starter includes everything in Personal, so the same per-file maximum applies. A file above 100 MB is outside the listed upload maximum and could block adding it.

Asana Pricing gives no history-retention window, covered event list or history-record export details for Personal or Starter. A 2020 Asana Community post reports its author's understanding that consecutive changes by one person to the same task property within 24 hours may be consolidated into one activity entry showing only the latest change.

Starter lists unlimited automations. A 2024 Asana Community update says the earlier 250 rule-action monthly cap no longer applies after Asana rolled back Starter limitations; the plan terms give no separate current action allowance or at-limit behaviour.

Asana Storage, History and Automation Limits (Personal and Starter Plans)

Read the vendor terms precisely

Asana Pricing distinguishes file size from storage volume: unlimited storage does not remove the 100 MB per-file maximum. It states no total or Workspace-level storage cap for Personal or Starter.

The reported 24-hour activity consolidation concerns whether changes appear as separate entries; it does not establish how long activity remains retrievable. The plan terms also do not say which events are covered or whether history records can be exported.

Unlimited automations is not an actions-per-month figure. Do not treat the 250-action monthly ceiling as a current Starter limit, and the supplied plan terms do not say what happens if another usage boundary applies.

Plan for the boundary

Check the largest files the project needs against the 100 MB maximum. If a required file exceeds it, confirm how it can be handled before relying on Asana for that material.

Name the activity events and retention period needed for project records, then confirm the Personal or Starter terms for those requirements, including exportability. Do not assume each rapid repeated property change will appear as a separate activity entry.

Estimate expected automation usage and confirm any applicable action allowance and what happens when it is reached. The listed unlimited-automations term alone does not establish an action threshold or whether a rule would stop running.

Planning Checklist for Asana Limitations