How to See Asana Rules Execution Logs via Asana Audit API Method. Any Endpoints to See

Asana Community API & Developers
1

Hello Asana Community,

We are part of the Asana Platform Support Team for an Enterprise environment and are looking for a way to monitor and troubleshoot Asana Rules (Automations) at scale.

While reviewing the announcement for the Audit Log API, we noticed that it provides visibility into many Enterprise administration, security, and governance events, but we have not been able to find any specific events or endpoints related to Rules / Automation execution logs. [forum.asana.com]

Our primary objective is to identify:

  • Rules that are failing during execution
  • Automations that are stuck in an error state
  • Rules requiring administrator intervention
  • Automation connections that require re-authentication
  • External app integrations used by Rules that may have become disconnected
  • Historical execution logs for troubleshooting and root cause analysis

We would like to know:

  1. Is there any Audit Log API event type that captures Rule execution outcomes (Success / Failure / Error)?
  2. Are there any undocumented or documented API endpoints available to retrieve Rule execution history or automation logs?
  3. Is there any way through the Audit Log API, Graph Export, or Developer APIs to identify Rules requiring re-authentication or manual administrator action?
  4. Has anyone built custom scripts or monitoring solutions to proactively detect failed automations in an Enterprise Asana environment?
  5. Are there any plans on the Asana roadmap to expose automation execution logs for Enterprise Administrators?

Business Use Case

As an Enterprise Asana Administration & Platform Support team, we need proactive visibility into automation health so that we can quickly identify and remediate failed workflows, expired authentications, and integration-related issues before they impact business processes.

Reference: Announcing Asana’s Audit Log API [forum.asana.com]

Any guidance, best practices, or recommended approaches would be greatly appreciated.

Thank you!
Pratik Parmar, Sr. Project and Program Manager
LTM Limited

2

Hi @pratikprojectltm and welcome to the forum,

FYI I moved your post to the forum section to discuss API related matters.

@Mikhail_Melikhov @Dominik_Brdak

3

Hi @pratikprojectltm ! Thank you for laying out the use case so clearly and welcome to the community!

There is currently no dedicated API or Audit Log API event types exposing Automations (FKA Rules) governance data.

The Agents > Automations tab in the new tabbed web layout gives fairly broad observability of automations:

  • By default the list shows only automations you own. Turn that filter off to see all automations accessible to you.
  • The list surfaces the state of each automation, so you can identify failing ones.
  • Sorting by last modified helps flag recent changes, which is useful when something starts failing after an edit.
  • Sorting by last activity helps identify automations that are no longer firing and may be unused.

It isn’t a replacement for programmatic monitoring or historical logs, but it’s a good starting point for general health checks.

For automations that run custom scripts, the lightweight approach that’s been working for me well is wrapping the whole script in a try/catch. In the catch block, post a comment on the task that triggered the script (storiesApiInstance.createStoryForTask) with the error details. This flags the failure right where the people involved will see it. It can potentially grow into a monitoring tool if you supplement it with service that watches for these error comments.

Thank you for raising this. Automation observability is definitely a valuable area to explore and improve.