Skip to main content

#Scheduled Path0 discussing

Greetings fellow Flow-natics,

I've got several record triggered flows with scheduled paths that send emails via email alert. These have stopped working. Sometime between 6/30 and now, this has stopped functioning.

 

The *exact same alerts* when used in a run immediately path send out fine, but any in a scheduled path do not. Is anyone else seeing this? Does anyone have a suggested way forward? Many thanks.

 

- The records debug correctly in the flow debug canvas

- The time-based workflows are created

- The email logs show no emails sent

- I recreated the precise conditions of the scheduled path in an immediate path and the emails sent out correctly

- Nothing in the audit trail to suggest a change that would affect these flows

Email Alerts in Scheduled Path Don't Send #Scheduled Flow #Scheduled Path #Flow #Email Alerts

8 answers
0/9000

I have created one Custom validation rule on Lead status field that will check if the Lead.IsConverted is true and the previous value of Status is not "Contacted" then It will display error. 

I want this because on the contacted status first I am killing all the time-based workflows and then I want to convert the lead so that the "Unable to convert lead that is in use by workflow" will not occur. But this won't happen, the "Unable to convert lead that is in use by workflow" will display if the time-based workflows are there and I am trying to change status from "Open" to "Converted".

 

Here I want to display my custom validation error before "Unable to convert lead that is in use by workflow" error.Is there any way we can do this? I also tried with Before Saved record trigger flow but that also not worked.

Is there any other work around we can achieve this?

0/9000

I currently have a situation where I am trying to get a scheduled path flow to run when either when the first two fields are filled in or when one pair of fields are filled in with both having a specific selection. 

 

Below is a screenshot of my conditions. 

 

Schedule Path - flow with OR statement?I feel like Scheduled Paths do not do well with or statements that are different fields, but I hope I am completely wrong. 

 

The issue here is if I have the NCS1 Status filled in and the NCS2 Status is then changed the flow does not run. 

 

#Scheduled Path  #Flow

5 answers
  1. Bradley Weller (Fast Slow Motion) Forum Ambassador
    Feb 27, 2024, 3:34 AM
    I’ve been trying to think of ways to pull this off with a single Flow. I expect you will have to break it into two Flows to pull off. You could either create two Flows, each with your different types of Entry Criteria or you could create a separate field and set that in a Fast Fields Flow when either of your criteria and are met, use that field as your entry criteria for your current Flow, and then reset the new trigger field at the end of your current Flow. I don’t love the two Flow approach, but I don’t see a way to pull it off in a single Flow.
0/9000

I have been trying to run a flow where I have selected for it to run the flow "Every time a record is updated and meets the condition requirements". Although, every time I try this I receive this error message:

$Record - This flow has a scheduled path with a time source based on when a record is created or updated. Configure the flow to run only when a record is updated to meet the condition requirements.

 

Can I run a Scheduled Path - Flow ever time a record is updated and meets the condition requirements?Are we only allowed to run the flow "when a record is updated to meet the condition requirements"? Or am I doing something wrong to get the flow to run every time conditions are met. 

 

#Scheduled Path  #Flow  #Salesforce Flow

2 answers
  1. Davis Johnson (SolomonEdwards) Forum Ambassador
    Feb 27, 2024, 12:22 AM

    @Manuel Rubio-McMillon,

    You are currently limited to using the "only when..." option with a scheduled path, although there are workarounds (see link: https://admin.salesforce.com/blog/2022/how-i-solved-it-run-a-flow-scheduled-path-based-on-a-field-change).

    If you are just looking to utilize async and don't actually need the time gap, checking the "async" path checkbox will work with the setup you described.

0/9000

Can someone confirm that a Scheduled Path that calculates to a time in the past when it's initially run will not be executed?

 

For example: let's say I have a Flow that sends a series of reminders before an event. I want the emails to be sent two weeks before, one week before, and one day before my event. So I create a record triggered Flow with three scheduled paths, and use the Start Date of the event as my Time Source.

 

What happens if someone registers for the event three days before the Start Date? In testing, it seems like the first two emails are not sent, but the final one is. Is that the expected behavior? Time-based workflow behaved differently, so I don't totally trust my testing.

5 comments
0/9000