Flow

Salesforce Flow engineering: record-triggered flows (before-save fast field updates, after-save related-record automation, before-delete), entry conditions and $Record__Prior, decisions and formulas, Custom Error, fault paths, subflows, autolaunched flows called from Apex, invocable Apex actions, scheduled paths, and choosing between flows and Apex triggers. Answers are Flow metadata files (API 67.0) deployed check-only to a clean scratch org, where hidden Apex tests do DML (including 200-record bulk tests that assert on Limits) and check the outcome.

18
tasks
Execution
grading
100%
highest c@3 · Claude Fable 5.1, joint first with 14 others
61
configurations with results

How it's graded

Flow metadata is deployed as a check-only validation to a clean scratch org, where hidden Apex tests do DML (including 200-record bulk tests that assert on governor limits) and check the outcome. Decision-guide questions (flow or Apex?) are multiple choice.

Difficulty mix

5 easy7 medium6 hard

Who's best at Flow

Within three attempts (c@3) on this suite only, with 95% confidence intervals. With 18 tasks the intervals are wide: where two overlap, those configurations are not clearly different. 1 finished configuration isn’t shown yet: its retries haven’t finished. Open in the full leaderboard →

Flow: c@3 by configuration with 95% confidence intervals
#Model and configScore c@3 · 95% CITasks
1Claude Fable 5.1 effort high
100%95% CI 82–100
18
1Claude Opus 4.8 effort high
100%95% CI 82–100
18
1Claude Opus 4.8 effort medium
100%95% CI 82–100
18
1Claude Opus 4.8 effort low
100%95% CI 82–100
18
1Claude Opus 4.8 thinking off
100%95% CI 82–100
18
1Claude Opus 5.5 effort medium
100%95% CI 82–100
18
1Claude Opus 5.5 effort low
100%95% CI 82–100
18
1Claude Sonnet 5 effort high
100%95% CI 82–100
18
1Claude Sonnet 5.5 effort high
100%95% CI 82–100
18
1GPT-5.6 Sol effort medium
100%95% CI 82–100
18
1GPT-6 Astra effort medium
100%95% CI 82–100
18
1GPT-6 Astra effort high
100%95% CI 82–100
18
1GPT-6.1 Sol effort high
100%95% CI 82–100
18
1Grok 4.6 effort high
100%95% CI 82–100
18
1Grok 4.7 effort high
100%95% CI 82–100
18
16Claude Haiku 5.5 effort high
94%95% CI 74–99
18
16Claude Opus 5.5 effort high
94%95% CI 74–99
18
16Claude Sonnet 5 effort medium
94%95% CI 74–99
18
16Claude Sonnet 5.5 effort low
94%95% CI 74–99
18
16Claude Sonnet 5.5 effort medium
94%95% CI 74–99
18
16GPT-6 Luna effort medium
94%95% CI 74–99
18
22Claude Sonnet 5 thinking off
89%95% CI 67–97
18
22Gemini 3.8 Flash effort medium
89%95% CI 67–97
18
24Claude Haiku 5.5 effort medium
78%95% CI 55–91
18
24Claude Haiku 5.5 effort low
78%95% CI 55–91
18
24Claude Sonnet 5 effort low
78%95% CI 55–91
18
27DeepSeek V4.1 Flash FP8 · effort high
61%95% CI 39–80
18
27DeepSeek V4.1 Flash EXL3 2.9bpw · vLLM + ExLlamaV3 · effort high
61%95% CI 39–80
18
29DeepSeek V4.1 Flash Native FP8, FP4 experts · SGLang · effort high
56%95% CI 34–75
18
29GLM-5.3 Flash EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · effort low
56%95% CI 34–75
18
31Inkling Small FP8 · effort high
44%95% CI 25–66
18
32GLM-5.3 Flash EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · effort high
33%95% CI 16–56
18
33GLM-5.3 Flash EXL3 4.0bpw experts, 4-bit dense · TensorFold · effort high
28%95% CI 13–51
18
33MiMo V2.6 Pro FP8 · thinking on
28%95% CI 13–51
18
33Mistral Large 4 effort high
28%95% CI 13–51
18
33Qwen3.8 Flash-Next NVFP4 · vLLM · effort medium
28%95% CI 13–51
18
37GLM-5.3 Flash FP8 · effort high
22%95% CI 9–45
18
37GLM-5.3 Flash EXL3 4.0bpw experts, FP8 dense · vLLM + ExLlamaV3 · thinking off
22%95% CI 9–45
18
37Nemotron 3 Ultra thinking on
22%95% CI 9–45
18
37Qwen3.8 Flash-Next MLX 4-bit · MTPLX · effort medium
22%95% CI 9–45
18
41Qwen3.8 27B AWQ-INT4 · vLLM · effort medium
19%95% CI 7–42
18
42Claude Haiku 4.5 thinking on
17%95% CI 6–39
18
42Claude Haiku 4.5 thinking off
17%95% CI 6–39
18
42DeepSeek V4 Flash Vision experimental FP8 + FP4 experts · vLLM · effort high
17%95% CI 6–39
18
42DeepSeek V4 Pro FP8 · effort high
17%95% CI 6–39
18
42Gemma 4 26B-A4B NVFP4 · vLLM · thinking on
17%95% CI 6–39
18
42Laguna S 2.1 FP4 · thinking on
17%95% CI 6–39
18
42MiMo V2.6 Flash FP8 + MXFP4 experts · SGLang · thinking on
17%95% CI 6–39
18
42MiMo V2.6 Flash FP8 · thinking on
17%95% CI 6–39
18
42Qwen3.8 27B MLX 8-bit · MTPLX · effort low
17%95% CI 6–39
18
42Qwen3.8 27B MLX 4-bit · MTPLX · effort low
17%95% CI 6–39
18
42Qwen3.8 Flash-Next MLX 4-bit · TensorFold · effort medium
17%95% CI 6–39
18
42Qwen3.8 Flash-Next INT4-AutoRound, 5 of 10 experts · TensorFold (Zig) · effort medium
17%95% CI 6–39
18
54Gemma 4 31B QAT W4A16 · vLLM · thinking on
11%95% CI 3–33
18
54Ling 3.0 Flash BF16 · thinking on
11%95% CI 3–33
18
54Nemotron 3.5 Lightning NVFP4 · thinking on
11%95% CI 3–33
18
54Qwen3.6 35B-A3B NVFP4 · vLLM · thinking on
11%95% CI 3–33
18
54Qwen3.8 27B AWQ-INT4 · vLLM · effort low
11%95% CI 3–33
18
54Qwen3.8 27B Splash 4-bit · Splash · effort low
11%95% CI 3–33
18
54Qwen3.8 27B AWQ-INT4 · vLLM · effort xhigh
11%95% CI 3–33
18
54Qwen3.8 Flash-Next thinking on
11%95% CI 3–33
18

What's in the suite

Solve rate is the share of finished runs whose first answer to the task passed (pass@1), a rough guide to how hard models find it. Difficulty is the task author’s label; from results is what the solve rate says: easy when two thirds or more of the finished runs pass it, hard at a third or fewer, once five have graded it.

Flow tasks with difficulty and solve rate
TaskDifficultyFrom resultsSolve rate
Autolaunched shipping quote flow called from Apexflow-shipping-quote-autolaunchedeasymedium
37%
Choose the tool for a reminder relative to a record dateflow-choice-close-date-remindereasyeasy
100%
Choose the tool for a same-record field updateflow-choice-same-record-updateeasyeasy
100%
Escalate breakdown cases with a fast field updateflow-case-breakdown-escalationeasymedium
37%
Welcome-call task for new customer accountsflow-account-customer-welcome-taskeasymedium
39%
Automation when a record is restored from the Recycle Binflow-choice-undelete-restoremediumeasy
85%
Block closing a case that still has open tasksflow-case-close-open-tasksmediumhard
31%
Call an invocable Apex credit check from a record-triggered flowflow-account-credit-check-actionmediumhard
21%
Close-date reminder on a scheduled pathflow-opportunity-close-reminder-scheduledmediumhard
29%
Create a delivery project when an opportunity is wonflow-opportunity-won-projectmediummedium
34%
Flag large opportunity amount swings using $Record__Priorflow-opportunity-amount-swingmediummedium
39%
Set a case SLA due date/time from its priorityflow-case-sla-duemediumhard
18%
Cascade an account discount to its open opportunities in bulkflow-account-discount-cascadehardhard
21%
Fault path that logs failed shipment creationflow-order-shipment-fault-pathhardhard
31%
Fix a flow that syncs account addresses to contactsflow-fix-account-address-synchardhard
26%
Invocable Apex contact matcher orchestrated by a flowflow-web-signup-contact-matchhardhard
27%
Record-Triggered Automation decision guide principlesflow-choice-guide-statementshardmedium
46%
Reusable onboarding subflow called from a record-triggered flowflow-account-onboarding-subflowhardhard
26%

Want this for your team?

Azul Labs runs Forcebench privately for two kinds of Salesforce team.

Choosing a model to run yourself?

A private benchmark of your shortlist

Open-weight models at the quantisations and reasoning efforts you could run on infrastructure you control, tested on your kind of Salesforce work, with a written recommendation.

  • Private tasks written from your work only ever run on local models; they are never sent to an API.
  • Re-testing after any change of model, quantisation or engine is available.
  • Typical turnaround is 2–3 weeks; large models take about a day of machine time per configuration.

Building or buying a Salesforce AI tool?

A private evaluation of your tool

Your tool on held-out tasks it has never seen, against API baselines (models reached through a hosted service) and Local ones (served on Forcebench’s own hardware), with a written report on where it holds up and where it fails.

  • It can start as a smaller pilot, about 30 held-out tasks with your tool against two baselines, before a full evaluation.
  • Repeat evaluations after your releases are available.
  • Typical turnaround is 2–3 weeks.

Fixed fee, quoted up front. The quote depends on the number of tasks and the number of models, tools or configurations tested.

Or email leo@azl.au · azl.au