Bulk Job Error Analysis & Retry Workflow

Overview

This scheduled flow inspects completed Salesforce Bulk API 2.0 jobs, separates successful from failed records, archives error rows to SharePoint, posts an HTML summary to Microsoft Teams, and optionally opens a new retry bulk job with only the failed rows.

Use Case

Bulk ingest jobs often fail partially due to validation errors, lock contention, or data quality issues. Manual post-processing is error-prone and delays recovery. This flow automates error analysis and retry, keeping failed data auditable in SharePoint while enabling self-healing retry loops without operator intervention.

The flow is ideal for teams that:

• Automatic post-processing of completed bulk jobs — no manual CSV analysis
• Failed records archived to SharePoint for compliance and future analysis
• Optional auto-retry with single-click configuration — failed rows resubmitted immediately
• HTML summary to Teams keeps ops team aware of job status
• Zero silent failures — every bulk job gets admin notification

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, set all eight env vars to your target Salesforce job, SharePoint site, Teams channel, and retry configuration, bind the three connection references (Salesforce, SharePoint, Teams), configure the SharePoint error folder (create manually if it doesn't exist), and turn the flow on.

Change schedule cadence

Edit the Recurrence trigger frequency — e.g., Minute interval 30 for 30-minute checks in test environments.

Multiple jobs per run

Replace the single flowlibs_SalesforceCompletedBulkJobId variable with a Dataverse table of queued jobs and wrap the core logic in Apply to each.

Custom error filename

Modify the Compose_Error_File_Name expression to add an environment prefix (e.g., 'prod-', 'uat-').

Turn off retry entirely

Set flowlibs_CF266_AutoRetryEnabled to any value other than 'true' to skip the CreateJobV2 → UploadJobData → CloseJob sequence.

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.

concat('BulkJob-', variables('varJobId'), '-FailedRows-', formatDateTime(utcNow(), 'yyyyMMdd-HHmmss'), '.csv')

or(equals(body('Get_Job_Info')?['state'], 'JobComplete'), equals(body('Get_Job_Info')?['state'], 'Failed'))

equals(toLower(variables('varAutoRetryEnabled')), 'true')

body('Create_Retry_Bulk_Job')?['id']

length(body('Get_Failed_Records_CSV')?['records'])