Skip to main content

Paused and Waiting Interviews : Salesforce warns about inactive user

We receive an email from Salesforce saying
Every waiting flow interview has an associated user — the person who caused the interview to start waiting. If that user is inactive, the interviews can't resume.John Doe (005xxxxxxxxxxxx) is inactive, so please delete the following flow interviews.
Without thinking too much I went straight away to the Process Builder to check if it uses hardcode Id referring to the inactive user and I found none. The process builder is fine.

The email was sent is to inform us that there some process builder on the waiting list and not able to get fired because it was created by an inactive user.

The user left the company for quite some time, how is possible for him to fire the process builder?

What is Paused and Waiting Interview? 
Paused and Waiting interview only applies on schedule action process builder or time-dependent action. You can check Paused and Waiting Interview at  Setup | Create | Workflows & Approvals | Flows and look at Paused and Waiting Interview section.

Why I receive the email above?
Because the process builder has Scheduled action to send an email alert on 15 days before Close Date. Let's say the Close Date is in next year and the process builder is fired this year. 

The action to send email will be listed in Paused and Waiting Interview. However, Salesforce will remove this interview from waiting list after it tried to execute once. I noticed that because when I clicked the link that provided in the email after investigation and the link is no longer available.
Data Not AvailableThe data you were trying to access could not be found. It may be due to another user deleting the data or a system error. If you know the data is not deleted but cannot access it, please look at our support page.
The email  just to warn us in case we got many more interview in pending that owned by the user.

What will happen if we deploy a new version of Process Builder while some of the previous version in pending list?
Any deactivated version Process Builder will continue as usual and Salesforce will not allow us to delete this version. Refer to link here. If we think the previous version should not run then we should go and delete the waiting list.

Some related links that you might find useful.


Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {