Start with the exact error and the flow type. Use Flow Builder Debug for eligible flows and Test Mode for autolaunched and record-triggered flows; for a real record-triggered failure, capture a debug log while reproducing the transaction. Check the Automation app’s Flow Monitor if an interview failed or paused. A successful debug run alone does not prove that a production save will work.
Choose the diagnostic tool that matches the flow
Salesforce’s recommended diagnostic mode depends on the flow type. Debug provides a step-through view of the path and resource values for eligible flows. Use Test Mode for autolaunched and record-triggered flows. For a record-triggered problem that occurs during a real save, debug logs show the runtime execution context that a narrower debug session may not reproduce. See Salesforce’s flow debugging guidance.
| Situation | Start here | What it can show |
|---|---|---|
| Screen or another eligible flow during development | Flow Builder Debug | Step-by-step execution and resource values; check rollback settings before running. |
| Autolaunched or record-triggered flow | Test Mode | Reusable test scenarios for the flow type. |
| Record-triggered failure during a real save | Setup debug logs | Execution sequence, element errors, transaction context, and limit details. |
| Interview stopped or paused | Automation app, Monitor tab | Failed interview details and debug view, or a control to resume a paused interview. |
Before a debug run, check whether rollback is enabled. A run without rollback can perform actions such as database changes (DML) and Apex execution; closing the run does not undo changes that were committed.
Capture the failure before changing the flow
Write down the exact error text, affected record and operation, approximate time, user or automated context, flow name and version if available, and whether the flow failed, paused, or apparently never started. Reproduce one narrow case at a time. Salesforce notes that logs can be large, so a focused reproduction makes the relevant execution easier to find.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Set up a runtime log for a real record-triggered error
- In Setup, open Debug Logs and create a debug level.
- Add a trace flag for the user or context that will reproduce the problem.
- Repeat the same record create or update that caused the error.
- Open the log associated with that reproduction and inspect the flow interview and error events.
Salesforce’s general debug-log guidance recommends setting Workflow to Finer when investigating flows. For the specific message “The record couldn’t be saved because it failed to trigger a flow,” Salesforce’s error-specific guidance recommends Workflow at FINEST. If the first log does not show enough detail, use the error-specific level and repeat the focused operation. See Salesforce’s debug-log guide and its failed-to-trigger troubleshooting article.
Find the first failing element
In the log, locate the flow interview start and follow the execution until the first relevant error. Use the message to identify the field, action, or resource involved; later errors may be consequences of the first one.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
- Governor-limit concern: inspect limit-usage events around the failure.
REQUIRED_FIELD_MISSING: note the named API field, then check the flow assignments on every relevant path and the object’s required fields. Required fields may be enforced by the system or by your organization. Salesforce explains this error in its required-field troubleshooting guidance.- Action or field error: inspect the element’s inputs and the values available on the path that reached it.
If the error email includes a flow version ID, Salesforce’s failed-to-trigger article describes using Tooling API metadata to identify the flow and element. Use read-only inspection when investigating metadata; avoid destructive REST operations.
If the flow appears not to start, check interviews and entry conditions
Open the Automation app and select Monitor to review failed and paused flow interviews. A failed interview’s detail view includes its error and can open debug details. A paused interview can be resumed when doing so is appropriate for the record and business process. The available monitoring behavior is described in Salesforce’s flow monitoring guidance.
Recommended Free Tools
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Also inspect the flow’s configured start conditions: confirm the record meets its entry criteria and that the create or update operation matches the trigger configuration. These are configuration checks, not proof by themselves that the flow ran; compare them with the affected record and operation.
Understand retries before waiting for another run
Do not assume every failure will retry. Salesforce documents retries at fixed intervals of 15, 30, 60, and 120 minutes for specified flow types and unhandled-error situations, including certain scheduled paths and after-commit or wait-based flows. Immediate before-save and after-save paths do not use that time-based retry. Check the type of flow and the failure context against Salesforce’s flow retry guidance.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Why a debug run can pass while production fails
Record-triggered flow debugging runs in rollback mode and tests a limited scope. Other triggered flows or processes can change how the complete transaction behaves, so a passing debug session is not conclusive evidence that the production save is fixed. Salesforce recommends testing outside debug in a sandbox and using actual debug logs to understand runtime behavior. See its guidance on flow testing and debugging.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test the fix and make the next failure easier to diagnose
Test safely in a sandbox
- Exercise each decision outcome, including the default path, boundary values, and unexpected values.
- Test fault paths and relevant user permissions.
- For record-triggered issues involving other automation, reproduce the real transaction outside Debug and inspect its runtime log.
Salesforce provides guidance on testing flows. Confirm behavior in the context of your org’s current release and the specific flow type.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Add useful fault handling
Salesforce recommends adding fault paths to elements that can fail. A fault path handles errors from the element it connects to; decide whether it should show a user-facing message, log useful details, or route the failure for review. Configure error notifications with relevant flow resource values so an owner or administrator has context to investigate. See Salesforce’s fault-path guidance.
Diagnose “The record couldn’t be saved because it failed to trigger a flow”
This message means a flow configured to run when the record is saved encountered a problem. Start with the flow error email, then create a debug log using the error-specific Workflow level and reproduce the save. Follow the log to the first failing element; if the error contains a flow version ID, use Salesforce’s documented Tooling API method to identify the flow and element. The steps and qualification for this message are in Salesforce’s troubleshooting article.
Quick Recap
Keep the investigation focused
- Capture the exact error, affected operation, time, and execution context.
- Choose Debug, Test Mode, Flow Monitor, or runtime logs according to the flow type and symptom.
- For a real record-triggered failure, diagnose the transaction with a targeted runtime log rather than relying only on a debug run.
- Test the fix across relevant paths and permissions, then add fault handling where failures need to be surfaced.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
