Improve Automation audit log duration to complete the rule to exclude the internal API/process time.

XMLWordPrintable

      Scenario: In the automation rule execution, the audit log shows the rule execution starts at 14:55:01 and ends at 14:55:03 but the log shows the total run time as 13.46s

      The difference you're seeing between the timestamps in the log entries (from 14:55:01 to 14:55:04, about 3 seconds) and the total reported automation run time (13.46 seconds) is expected 

      The "run time" reported by the automation rule reflects the total time taken by the rule engine to process the entire automation, including all actions, conditions, and any background processing. This includes:

      • Time spent waiting for system resources or API responses
      • Any internal queuing or processing delays
      • Time taken by actions that may not generate visible log entries (e.g., waiting for webhooks, integrations, or rate limiting)

      Suggestion: The daily throttling threshold and token calculation should be based on the actual execution time of the rule logic (the 3 seconds), and must exclude the time consumed by Atlassian's internal queuing, resource allocation, or API wait times.

            Assignee:
            Unassigned
            Reporter:
            Saurabh Kapoor
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: