function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Tanner Cannon 10Tanner Cannon 10 

Flow Elements Not Resuming as Expected

Hi,

I'm running into an issue where my shceduled actions are not completing as expected.

We have a custom object NPS_Survey__c which is fed data through a third party survey tool.
On create of a record several things happen using Process Builder.
  1. parse the survey into fields on the record using Flow to include
    • Survey End Date (date) = date survey submitted on
    • Last Day of Month (FF)
    • Last Day of Next Month (FF)
    • isCurrentMonth (checkbox) = True
    • isLastMonth (checkbox) = False
    • isCurrentYear (checkbox) = True
    • Last Day of Year (FF)
  2. schedule an action to update isCurrentMonth__c to False based on Last_Day_of_Month__c that gives last day of the month the record was created in
At the end of a given month, all of the NPS_Survey__c records created in that month are scheduled to be updated so that...
  1. isCurrentMonth__c = False
  2. isLastMonth__c = True.
At the end of the next month all of the NPS_Survey__c records are scheduled to be updated so that...
  1. isLastMonth__c = False
Finally, at the end of the Year all of the NPS_Survey__c records are scheduled to be updated so that...
  1. isCurrentYear = False
This process works for us however I believe we are hitting limits on the number of paused interviews etc.. and thousands of my records are not updating properly. Not quite sure how to tell if this is the case or not. 

In a given month we may recieve 2,500 to 4,000 new surveys which get added to the queue.

My understanding based on this article is that we are most certianly hitting the limits.
https://help.salesforce.com/apex/HTViewHelpDoc?id=vpm_admin_flow_limits.htm&language=en_US

Looking for a way to verify what the root cause of the issue is and best practices on how to handle this type of operation using the visual workflow.

Thanks,
 
SF ABCSF ABC
Hi Tanner,

Just saw the question.
Not sure how exactly you are defining the time-based triggers, but it seems you can have up to 24,000 time-based triggers a day (1,000 per hour, 20,000 at a time).  If you hit the limit, time-based triggers won't be fired as expected.
I think you may need to optimize your process builder to make the criteria more specific. For example, the sample criteria can be: 
OR
(
/*criteria for records of current month*/
(
isCurrentMonth__c,
Not(isLastMonth__c )
)
,
/*criteria for records of last month*/
(
Not(isCurrentMonth__c),
isLastMonth__c,
)
,
/*criteria for records of this year*/
isCurrentYear
​)