Asana Stuck-in-Section SLA Escalation

Overview

This flow stops Asana work stalling silently between workflow stages. On a daily schedule it lists the tasks in a monitored Asana project, reads each open task's activity stories to find which section it currently sits in and when it entered that section, and compares that dwell time against a per-section SLA. Tasks past their section SLA get a timestamped comment on the task and a nudge to the team's Teams channel; tasks past the SLA by an escalation multiplier (e.g. 2x) are additionally escalated to the lead by email.

Why it matters: Tasks rot in interim sections (In Review, QA, Blocked) where no due date applies, so deadline-based alerts miss them. Section-level SLAs catch the silent stalls that deadlines can't.

Status: Built; ships Off (demo). Going live requires only connection authorization, the Asana API token, and env-var configuration - the wiring is complete.

Use Case

A team that runs an Asana board with workflow sections (e.g. To Do -> In Progress -> In Review -> QA -> Done) wants any task lingering in a stage longer than that stage's agreed SLA to be surfaced, nudged, and - if badly overdue - escalated, without anyone manually policing the board.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Asana	shared_asana	ListTasks AddComment
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Tune the section SLAs

Edit flowlibs_SectionSlaMap; any section not listed is never flagged (it gets an effectively-infinite SLA), so you can scope the flow to just the stages you care about.

Change the escalation threshold

Raise/lower flowlibs_EscalateMultiplier (e.g. 3 = escalate at 3x the section SLA).

Re-time the sweep

Adjust the Recurrence trigger (e.g. twice daily, or hourly for fast-moving boards).

Add WIP limits

Combine with a per-section task-count check to flag overloaded stages.

Auto-reassign

Extend the Far Past SLA branch to reassign stuck QA tasks via Asana.

Trend reporting

Log each breach to Dataverse to report average time-in-section per stage over time.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@last(body('Filter_Section_Change_Stories'))

@outputs('Compose_Section_Entry')?['new_section']?['name']

@div(sub(ticks(utcNow()), ticks(outputs('Compose_Section_Entry')?['created_at'])), 36000000000)

@coalesce(json(variables('varSectionSlaMap'))?[outputs('Compose_Section_Name')], 999999)

@greater(outputs('Compose_Hours_In_Section'), outputs('Compose_Section_SLA'))

@greater(outputs('Compose_Hours_In_Section'), mul(outputs('Compose_Section_SLA'), int(variables('varEscalateMultiplier'))))

Customize & download