Stale Bulk Job Auto-Cleanup

Overview

This scheduled daily flow monitors Salesforce bulk jobs for stale operations running longer than a configurable threshold (default 24 hours). When stale jobs are detected, the flow automatically aborts them and posts a detailed cleanup summary to a Microsoft Teams admin channel. If no stale jobs are found, it posts an all-clear confirmation message.

Use Case

Salesforce bulk API jobs can occasionally get stuck in an InProgress state due to API timeouts, lock contention, or malformed data batches. Left unattended, these stale jobs consume API limits and can block subsequent bulk operations. This flow automates the detection and cleanup, ensuring Salesforce bulk job queues remain healthy without manual intervention.

The flow is ideal for teams that:

• Automatic daily scan for stale jobs — no manual monitoring needed
• Automatic abort on detected staleness — frees up API limits and queue space
• Detailed cleanup report to Teams — ops team stays informed
• Configurable staleness threshold — adapt to your environment's needs
• Zero-error flow — uses only hard-coded object names and env vars for flexibility

Flow Architecture

Environment Variables

Connectors & Connections

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.

Deploying to another environment

Import the solution, update the four env vars with your target Teams group/channel and IT team email, bind the Salesforce and Teams connection references, then turn the flow on. The first run happens daily at 6:00 AM EST.

Adjust the stale threshold

Change flowlibs_SalesforceStaleJobThresholdHours (for example, 12 for a 12-hour threshold or 48 for a 2-day threshold).

Change notification channel

Update flowlibs_AdminTeamsGroupId and flowlibs_AdminTeamsChannelId to point at your preferred admin Teams channel.

Filter by a different job state

Modify the Filter Array condition to target other states (for example, 'Queued' instead of 'InProgress').

Add an email notification

Insert an Outlook SendEmailV2 action after the Teams post to send an email alert to the IT team in addition to the channel message.

Change schedule

Adjust the Recurrence trigger frequency — for example, run every 2 hours for more aggressive monitoring instead of once daily.

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.

addHours(utcNow(), mul(variables('varThresholdHours'), -1))

and(equals(item()?['state'], 'InProgress'), less(item()?['createdDate'], outputs('Compose_Cutoff_Timestamp')))

replace(replace(replace(string(body('Select_Job_Summary')), '{"html":"', ''), '"},{"html":"', ''), '"}', '')

greater(length(body('Filter_Stale_Running_Jobs')), 0)

int(variables('varThresholdHours'))