I want to follow up on my previous question. Because of some version issues with process builder, we wanted to move some apex action invocation to record-triggered flow with scheduled path. The condition to trigger this flow is Status = waiting for approval. Then we have an approval process which in its initial submission action have field update wf which sets Status = waiting for approval and the re-evaluation is set to true, but the flow is not triggered.

Is this some feature or bug?

  • 2
    it is a known issue Aug 5, 2021 at 20:03
  • thanks for the know issue
    – Damecek
    Aug 6, 2021 at 8:37
  • Just commenting here to say this also applies to Before-Save RT Flows, although the Known Issue currently says it's only for After-Save Flows
    – dschib
    Sep 14, 2021 at 10:24

2 Answers 2


This has been fixed as of Spring '22

  • Note that if you have an existing Record-triggered flow that was created before Spring '22, you need to resave it using the Spring '22 'API Version' of 54 (or higher) in order to have it trigger this way. (See drive.google.com/file/d/178CjjDB5obFdVQnKBTwZQSO64gnFZcz2/…) Salesforce did this so that existing flows wouldn't suddenly start triggering unexpectedly. Jan 9 at 15:20
  • a record-triggered flow which I just created in a sandbox org, and is using API v54, is still not being triggered upon an update made by an approval process field update. Any idea why the fix isn't working for me?
    – Garywoo
    Jan 25 at 20:22
  • This known issue seems to not apply to scheduled paths. I've done extensive testing and while the "Run Immediately" path works just fine as of Spring '22 (v54) I have not been able to find a workaround (besides using PB) to trigger a scheduled path from an Approval Process field update.
    – Tomulent
    Feb 25 at 1:00
  • 1
    @tomulent, what you're referring to has just been fixed so it should get patched into Spring '22 in the next two weeks. Garywoo, my guess is you might be getting hit by the same issue with async paths. Feb 25 at 15:45
  • Can confirm it was fully patched as of 3/3/2022 (trailblazer.salesforce.com/issues_view?id=a1p4V000000pOrNQAU)
    – Tomulent
    Mar 15 at 16:02

As per Kris Goncalves it is known issue.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.