How We Accidentally Burned Through 4 Million Asana AI Studio Credits in a Month 🤯 …and how you can avoid doing the same.

[Bastien_Siebman]

At iDO, we hit the AI Studio usage limit — hard. We reached more than 4 million credits in a month, which disabled our AI rules until the next renewal!

Here’s what happened (and yes, it’s a mix of bad luck and bad processes on our end):

No dashboard = no visibility

We made the beginners mistake of not looking at our AI Studio usage dashboard. We did receive the warning messages but it was too late: we should have been proactive.

A costly My Tasks rule

One teammate had a rule using one of the most expensive AI models.

1. Sometimes cheap per task, but occasionally very expensive

2. No conditions to limit when it ran → triggered on every task assigned to them

The “I’m on holiday” automation fail

I wanted to be email-free for 2 weeks, so I:

1. Forwarded all my emails into Asana

2. Created tasks automatically

3. Let AI decide priority & next steps

The problem?

1. Some of those emails were Asana notifications from another account

2. They got forwarded, created tasks, triggered more notifications, sent more emails → endless loop

3. AI ran every. single. time.

I set it up on a Friday, left my laptop behind, and never checked back. My colleague spotted it quickly, killed the rule… but too late.

The takeaway?

Monitor your AI Studio usage in the admin console

Add specific conditions to your AI rules

Test any automation that could loop before you disappear on holiday

Don’t go too “AI first” for simple rules.

If something can be handled by a native automation, there’s no need to hand it over to AI.

And if it’s too complex for a standard rule, a Custom Script can be a great alternative.

In short: “AI is sometimes a bazooka to kill a fly.”

We’re actually glad this happened to us as an Asana Solutions Partner — now we know exactly what to warn our clients about.

---

Bastien, Asana Expert
i.DO (Asana Partner: Services & Licenses)

[Rebekah_Chalkley]

Hey, somebody’s gotta test the limits for the rest of us, right?

I heard recently that the concert pianist Franz Liszt would demand two grand pianos to be placed on the stage for every concert. He would break so many strings on the first piano that after the intermission, he would play the second piano and break all the strings on that one, too.

I kind of feel like Liszt did a kindness to all the rest of the pianists who came later, because his abuse of pianos undoubtedly prompted Steinway & Sons (and other manufacturers) to figure out ways of making pianos more indestructible. Today, they use steel frames for the strings, which can support a lot more tension.

So - thanks for being our Franz Liszt on this one! LOL

[Arthur_BEGOU]

@Rebekah_Chalkley
Thanks for that comment, so cool to read.

@Bastien_Siebman is definitely a virtuoso in his art

[Bastien_Siebman]

Our pleasure

[ka_nishiyama]

Asana is actively recommending the use of AIStudio.
Like this.

Introducing AI Studio: proactive rule suggestions - Smart automation recommendations tailored to your workflows!

Hi everyone, We’re excited to introduce a new way to save time and reduce manual work with Proactive rule suggestions in AI Studio. This feature helps you identify automation opportunities based on patterns in your team’s workflow, making it easier to streamline your processes without extra effort. Some of you may have noticed this earlier during the rollout, but it’s now fully available to all eligible users! Here’s how it works: Asana analyzes the actions yo…

It’s a very good initiative, but I feel like it’s being rushed.

In addition to recommending its use, I would also like them to provide follow-up support to practitioners.

[Bastien_Siebman]

@ka_nishiyama

It’s a very good initiative, but I feel like it’s being rushed.

I wouldn’t say it’s being rushed, but I feel like sometimes Asana is pushing for AI when a clean native automation will do the trick. And I know that Asana doesn’t agree with me, but I usually push for AI to be added on top of a clean and working environment, meaning that you have to master Asana before using AI too much. And I know that Asana wants to use AI as a way to make it easier for people to discover and use Asana.

[June_LCG]

There needs to be a way to limit the number of actions that an AI automation can make during the testing/building phase to prevent infinite loops, like AIs endlessly commenting to each other, an easy mistake to make while iterating/testing. How to request this as a feature? I burned through 10% of a month’s credits in 90 seconds yesterday, and deleted it immediately only because I had the billing/AI usage open in another browser window alongside…. Notice I said deleted - it wasn’t possible to halt it.

[Arthur_BEGOU]

That’s a good idea.
Feel free to create a post in the category ‘Product Feedback’.
People will be able to vote for it

[June_LCG]

Thank you just did! Please vote Create a way to limit # of actions of an AI rule during testing/iteration phase to prevent infinite loops

[Bastien_Siebman]

FYI, our post was made some time ago, and Asana might have put in place new protections against such a situation.