Obervability
Services AudiTrace Resources▾ Contact
Book a free audit
Audit domain · 2 checks

Dynatrace workflow audit: automation that fails or never fires

Two checks on AutomationEngine workflows — execution history and failure rate, and workflows whose trigger conditions can no longer match anything.
Book a free audit All 71 checks

What these checks read

Execution and failure history

Every workflow, when it last ran, and its recent success rate.

Unreachable triggers

Workflows whose trigger references an entity, tag or profile that no longer exists.

Why it matters

Automation that fails loudly gets fixed. Automation that fails silently gets trusted, which is worse: the runbook step that says "the workflow handles this" is still in the runbook, and the workflow has been erroring since a tag was renamed in March.
The checks read execution history and trigger configuration. A workflow that has never run since creation is usually a trigger that cannot match; a workflow that runs and fails is usually an integration credential. The finding says which of the two you have, per workflow, with the last successful execution.
This domain is small — two checks — and it is frequently the one that produces the most immediately actionable finding, because a broken workflow has an owner and a fix measured in minutes.

Questions we get about this domain

Does the audit execute any workflows?

No. It reads their configuration and their execution records. Triggering a workflow could page someone or change something, which is exactly what a read-only audit must not do.

We run very little automation — is this domain relevant?

Then it takes two checks and reports that, which is a useful thing to have in writing. The audit reports "not applicable" honestly rather than manufacturing findings to fill a section.

The other audit domains

Nineteen domains, 71 checks, one read-only run. Each domain is a page.
FinOps Where the money goes, and what is recoverable Kubernetes Cluster coverage, versions, recurring failures Alerting Whether an incident would actually reach a human Audit log Who changed what, when, and outside business hours Coverage What is monitored, what only looks monitored RUM Real-user monitoring reach and privacy settings Grail Buckets, retention, annualized storage cost Pipelines Ingest processing, masking, drop rules Synthetic Synthetic monitors that pass, fail, or never run Topology Entity detection quality and entity explosion OpenTelemetry OTel sources and dual instrumentation Security Token scopes, expiry, dormant credentials Workflows Automation that fails or never fires Bizevents Business event provider hygiene Dashboards Dashboard inventory Davis Root-cause attribution rate OpenPipeline Route and pipeline resolution SLO SLO definitions that break on re-detection Tagging Environment tagging convention

See what this domain finds on your own tenant.

One read-only run covers all nineteen domains. You keep the report either way.
Book a free audit See how AudiTrace works

Find out what your Obervability is actually doing.

An audit takes one run. The findings take one meeting. What you do with them is up to you.
Certified Dynatrace experts
+1
Send
Obervability
Dynatrace implementation, managed services and support. Every finding comes with the source behind it.
Services
Services AudiTrace Case study
Guides
Dynatrace audit Dynatrace cost optimization Audit case study Articles
Reach us
© 2026 Obervability · All rights reserved.
Privacy Terms of use Accessibility