I’ve had so much encouragement from your various in-app notifications the week to make me start to actually try using this function and when I finally take the time to look into it, I realise how completely limiting it is to have only 20 rules!
1 Like
I agree! With the limitation, some of our Asana processes still have to be manually actioned on.
1 Like
Any update on this? With the new Workflow builder making it easier for our teams to automate their processes we’re finding it even more difficult to truly build out processes with the 20 rule limit. For simple processes on small teams, it works. For more complex processes or larger teams, it’s impossible!
Begging you here, PLEASE increase this limit!
4 Likes
It would be great to hear whether there is a plan to increase the rules limit or increase the functionality of a single rule. I copied the rules from a template to have custom fields be set when tasks are moved between sections and have the section move when the custom fields are set, but that takes up 2 rules per section, so I hit the limit of 20 rules VERY quickly which is limiting the functionality of the automation potential severely
This is true for smaller companies too… we can have complex workflows…
Just hit the limit today building out the second workflow using the new workflow builder, and already disappointed by this arbitrarily low limit.
Will now see if I can “string together” several projects to do what I should be able to do in one. Sigh.
+1 on this. I was so frustrated when I was three rules away from finishing my workflow and realized I would have to split into separate projects (which I’m not even sure I can do). I’m now thinking of housing this project in another platform despite loving Asana 
You might want to check out our Flowsana integration; it has no limit on rules per project so perhaps it could allow you to stay with Asana…
1 Like
I work at a small not-for-profit (2 staff) using the business plan.
I just built out a candidate tracking workflow and I was super excited to start using it, as I immediately saw positive returns (less time spent on the recruitment process/stages, everything in one place, etc).
As I was adding more rules to tighten up this workflow, I hit the 20 rule limit. This is quite frankly disappointing… considering we are a small shop and need this functionality as there are certain ways you can miss important work by not automating it the first time.
Please consider increasing this limit.
Thank you,
Alex
2 Likes
I don’t understand why the go-to response to many requests is to use Flowsana. It is seemingly becoming the catch-all answer for everything. Flowsana is not that great. We tried it for a few months. The fact that I have to keep updating each project from inside Flowsana when we have an update is ridiculous and even more infuriating that the 20 rules limit in Asana. Updating projects inside Flowsana is fine at first. However, it is nowhere near scalable. Adding insult to injury is the fact that there is an additional cost for Flowsana and no matter how nominal it seems to be initially, it does grow with how many projects you run workflows on. Also - just my two cents here - Flowsana LACKS in teaching anyone how to use it.
1 Like
Wow do I feel this. At least with additional projects you get an additional set of 20 rules but I am with you… now not only am I chasing tasks but projects as well. And, they’re not really projects; just housing for additional rules.
Hi @anon97555450,
Trust me, I get your frustration! Just wanted to make a few clarifying comments…
Believe me, I wish that wasn’t necessary; but Asana does not notify external integrations of changes in custom fields, tags, or users, so there’s no way for Flowsana to pick those changes up automatically.
Just to be clear, the Flowsana cost is not directly related to number of projects, but to number of team members in teams having workflow-enabled projects. So adding more workflow-enabled projects in a team won’t increase the cost. Adding workflows to additional teams will, if those teams have members that are not in the existing teams that have workflows. Hope that’s clear.
In addition to our online Knowledge Base, we do offer a complimentary online introductory session (but you’re right that’s not publicly stated, it’s more on-demand-as-needed). I do agree that some videos are warranted and that’s on the to-do list!
Having said all of that, I agree that I think Asana should allow for more than 20 rules per project!
This would be so helpful!
We hit this issue. Asana premium with 70+ seats needs this one to continue working with Asana!
Hi All 
- my go to, interim solution, not flowsana based, is to add ‘ghost projects’. Steps below:
- In original project (OP), the custom fields used in the rules must be added to the library;
- Create a ghost project, e.g. “Ghost - Risk Register” (a) make it grey (b) add custom fields
- Add a rule to the OP that says “when new task added” >> “add to ghost project”
- In the ghost project, start to add your rules.
So for example I wanted to create a risk register and I wanted to automate the risk rating based on the likelihood and consequence ratings (this equates to 25x individual rules). So I have a main risk register and then two ‘ghost’ risk registers.
This does not work for all types of rules you may want to add of course, but can be a great work around.
The other solution is that you can use the “If any of these things happen” rather than “If all of these things happen” … which has enabled me to condense say four rules in to just one.
2 Likes
Hi folks,
I’m excited to share that we’re increasing the limit of rules per project from 20 to 50 
This update should enable you to automate all your processes, including the most complex ones. Please note this update is rolling out to 30% of our customers today. Providing we don’t identify any bug, it will become available to everyone on Mar 21st!
We can’t wait to hear your feedback and hope this will enable you to do more in Asana!
18 Likes