Running on Asana?

Asana rules firing wrong or portfolios lying? We clear the backlog.

Asana handles work until a project reaches 20,000 tasks and every rule in the account suddenly looks suspect, a webhook starts duplicating tickets after an outage, or a custom field renames itself halfway through a rollup. We trace the rule triggers, the API retries and the portfolio dependencies until the numbers in the dashboard match the work on the ground.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

asana-rules.log

still misfiring

What it is

Asana at a glance

Asana is a work management platform founded in 2008 by Dustin Moskovitz and Justin Rosenstein, both ex-Facebook. It offers task lists, boards, timelines, calendars, portfolios, goals and workload views, and is one of the most widely used project management tools for mid-market and enterprise teams.

The platform covers tasks, subtasks, sections, custom fields, rules (if-this-then-that automation), forms, dependencies, approvals, portfolios for rollups across many projects, goals for OKR-style tracking, and an admin surface with SAML SSO, SCIM and audit logs on the Enterprise tier. There is a REST API, webhooks, an events stream and integrations with Slack, Microsoft Teams, Google Drive, Salesforce, Jira, Figma, Zapier and many others. The issues we see tend to cluster around rules that fire too often or not at all, portfolios that lag or show wrong rollups, API throttling during bulk work, and the occasional CSV import that silently drops rows.

Type
Work management and project collaboration platform
First released
2012
License
Proprietary SaaS, per-seat pricing with Basic, Starter, Advanced, Enterprise and Enterprise+ tiers
Maintained by
Asana, Inc.
Typically used for
Project management, cross-team work, goals tracking, portfolio reporting, workflow automation

The honest version

Asana pros and cons

No technology is all upside. This is where Asana earns its place and where it tends to cause trouble.

Where Asana is strong

  • Multiple views out of the boxLists, boards, timelines and calendars all point at the same underlying tasks, so different roles can look at the same work the way they prefer without creating duplicates.
  • Rules without needing ZapierBuilt-in automation covers field changes, status transitions, task assignment and notifications, which handles most of the glue work that other tools push to external integrations.
  • Portfolios roll up across projectsA program manager can see status, risk and progress across dozens of projects in one view, which beats maintaining a slide deck of screenshots.
  • Good forms-to-task pipelineExternal requests land as tasks with structured custom fields, routed to the right project, which turns intake requests into trackable work instead of inbox threads.
  • Strong API and webhooksThe REST API is well documented, webhooks are reliable, and the events stream lets you reconcile without polling, which makes integrations worth building.
  • Enterprise administration is seriousSAML SSO, SCIM provisioning, audit logs, data residency and service accounts make the platform acceptable to security teams in regulated environments.

Where Asana bites

  • Rules get out of hand fastAny admin can create a rule, nothing enforces review, and workspaces accumulate hundreds of rules referencing deleted fields or long-departed users. Debugging why a task moved is painful.
  • Per-seat pricing is punchyAdvanced and Enterprise tiers add up quickly, especially when teams pay the editor rate for occasional contributors who open one task a quarter.
  • Reporting is shallowThe built-in dashboards do basic counts and charts; anything cross-cutting (burn-down, velocity, cycle time) usually needs export to a BI tool, which is more work than Asana implies.
  • Custom fields are global, which hurtsChanging a field value on a workspace library scope cascades everywhere, and renaming or deleting a field is a one-way action that breaks saved reports and rules silently.
  • API rate limits are modestThe default limits catch bulk imports, migrations and nightly sync jobs. Work around them with batching and backoff or expect to spread an import over days.
  • Portfolio rollups lagRoll-ups update asynchronously, so a status change in a project may take minutes to appear at the portfolio level. The lag is small in practice but looks wrong to executives expecting live numbers.

Sound familiar?

Common Asana problems we fix

The Asana problems that bring people to us, and what you have once each one is fixed.

429 rate limit exceeded

A bulk import or sync hits the API ceiling

A migration script writing tasks at full speed with no throttling, or a nightly sync that grew past the budget as the workspace scaled. The job fails partway through and leaves tasks half-populated.

Sync respects limits, resumable

rule did not fire: field deleted

Automation rules reference deleted fields or users

A custom field renamed or removed, or a user who was deprovisioned but is still referenced in rule assignments. Rules fail quietly and nobody notices until a task does not move the way the workflow document says it should.

Rules audited, references cleaned

project exceeds 20000 tasks

A project is too large to duplicate or export

A project that accumulated tasks for years, hitting Asana's per-project ceiling. The project becomes slow to open and refuses to duplicate for archive or templating.

Project split, archive clean

portfolio rollup incomplete

Portfolio shows stale project statuses

A portfolio with many projects, some of which have not had a status update in days, so the rollup color is based on outdated signals. Leadership makes decisions on numbers that are no longer true.

Rollup fresh, cadence enforced

webhook retry attempt 3 of 5

Webhooks are retrying and duplicating work

A consumer that returns a non-2xx status because of a transient downstream error, triggering Asana's retry logic. Without idempotency, the same task event is processed twice or more.

Webhook handler idempotent

parent task in different workspace

Cross-workspace moves break parent/child links

A task moved between workspaces that leaves subtask relationships in an invalid state, or an integration that attempts to create a child in a workspace where the parent does not exist.

Hierarchy preserved across moves

CSV row 234: value not in allowed list

A CSV import drops rows silently

An enum custom field whose allowed values do not match what the CSV contains, so a subset of rows import with missing fields rather than failing the whole file. The data looks clean until you audit it.

Import validated row by row

SAML JIT provisioning disabled

New hires cannot log in via SSO

A SAML configuration where just-in-time provisioning was never enabled, so new users have a valid IdP session but no Asana account, or a SCIM pipeline that silently fails.

SSO and provisioning aligned

What we do

Asana help, rules to portfolios

Call us for one misfiring rule, or let us own the whole Asana workspace configuration.

Rescue
Rules firing in a loop, a portfolio showing wrong numbers, or an import stuck halfway through. We stop the bleeding first and then explain the cause.
Rules and automation audit
Rule inventory against current fields and users, consolidation of overlapping rules, and a convention for who can create rules and how changes are reviewed.
API integrations
Custom webhooks, event stream consumers, Slack and Teams bots, and data pipelines into the warehouse, all built to respect rate limits and survive retries.
Portfolios and reporting
Portfolio design, custom-field taxonomy and dashboards that give leadership the view they actually ask for, plus a warehouse export for the BI tool.
Migrations
Moving from Jira, Monday.com, ClickUp or Trello into Asana (or out of it), with templates recreated, custom fields mapped and workflows tested before the full switch.
Managed Tech
Monthly rule audits, portfolio health checks, API integration monitoring, and an engineer available when a release changes the rule engine or the API behaviour.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Asana alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Asana questions

Something else? Call+1 737 727 7327

Why are our Asana rules firing at the wrong time?

The most common causes are rules that reference custom fields which were renamed or deleted, overlapping rules whose order of evaluation is not what the admin expected, and conditions written against user groups that have shifted in membership. We inventory the rules, map each trigger to a current field, and remove the duplicates so only one rule owns each outcome.

How do we handle Asana API rate limits for bulk work?

Batch, backoff and record. Use the batch endpoints where they exist, implement exponential backoff on 429 responses, keep a persistent checkpoint so a failed job resumes rather than restarting, and target well under the per-minute ceiling to leave headroom for live traffic. For very large imports, we split the work into phases and run them overnight.

Why does our Asana portfolio show the wrong rollup color?

Portfolios aggregate status from the underlying projects, and a project with no recent status update will drag the rollup toward the last reported value. We check that each project has a cadence (weekly status posts), that the status field in the portfolio maps to the project status, and that leadership understands the rollup is a reported snapshot rather than a live count.

Can we migrate from Jira or Monday.com into Asana without losing history?

Mostly yes, with care. Tasks, comments, assignees and custom field values transfer through the API. Attachments transfer as copies rather than moves, time tracking and sprint history do not come across natively, and we usually recommend archiving the source system read-only rather than deleting it. We run the migration on a sandbox workspace first.

How do we build a reliable Asana webhook consumer?

Verify signatures, respond with a 2xx quickly and process asynchronously, make the handler idempotent so a retry does not duplicate work, and record every delivery so you can tell the difference between a bug in the consumer and an Asana outage. A consumer that follows those four rules survives the normal failure modes without manual intervention.

How much does Asana help cost?

A quote is free. Describe the workspace tier, the symptom and any integrations in play, and we come back with a scope and a fixed price before anyone logs in.

Free estimate

Asana giving you trouble?

Rules audits, portfolio reporting, API integrations and migrations in and out of Asana. We work on the workspace, not just one project.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.