Asana rule triggers on opening status update, not posting

English Forum Ask the Community
1

Hi everyone :waving_hand:

I wanted to check whether others have run into this behaviour and whether it’s expected or there’s a recommended pattern to handle it.

We have a portfolio‑level rule that is designed to fire when a status update is posted (i.e. when someone actually submits a post).

What we noticed is that:

  • Simply opening the status update window

  • Or navigating away without posting

…can still cause the rule to fire, even though no status was actually submitted.

So effectively, the rule is reacting to “opening/editing” activity rather than a clear post/submit action.

  • Have others seen the same behaviour with portfolio‑level rules?

  • Is this expected behaviour when opening the status update UI?

  • Are there best‑practice patterns for reliably distinguishing draft / open vs submitted post?

Keen to hear how others are handling this, or if there’s a more native approach we should be using.

Thanks!