Skip to main content
GroupsMass Action Scheduler
Group

Mass Action Scheduler

This group has been created to support discussion around this tool. This is a community powered tool so questions may not get answered immediately. http://bit.ly/MassActionScheduler
Ask a question...
Steve Pysnik (Principal Consulting Manager at Cloud Giants)
Jun 5, 1:33 PM
How to set up Mass Action now that Connected Apps aren't allowed?

I recently installed Mass Action Scheduler in a sandbox. I went to the Authentication Setup Wizard (Mass Action Auth. Setup tab) and the Automated Setup button no longer works because it tries to create a Connected App, which Salesforce no longer allows. So, I followed the manual instructions in GitHub and created all specified metadata: Auth Provider, Named Credential, and swapped out an External Client App for the Connected App steps. However, when I go to create a new Mass Action Configuration, I get an error saying that it can't find the Named Credential (API name of my credential is Mass_Action). I am a System Admin and I have the Mass Action Admin permission set assigned. What am I missing?

2 answers
  1. Rahul Chauhan (KCT)
    Jun 7, 10:19 AM

    It sounds like the package isn't recognizing the Named Credential you created.

    I'd double-check that the API name matches exactly what Mass Action Scheduler expects and that the Named Credential is active and saved properly.

    Since Salesforce changed how Connected Apps work, it's also possible the package hasn't been fully updated for the new External Client App setup.

    If everything looks correct, I'd check the package's GitHub issues or documentation to see if there are any known issues with the latest Salesforce changes.

Write an answer...
0/9000
Swathi Paladugu (Genpact)
Apr 30, 2024, 3:44 PM
Can any one suggest Mass Action Scheduler Replacement tool for Salesforce ?
9 answers
  1. Matthew Steiner (The CRM Firm)
    May 1, 2024, 2:40 PM

    A big reason a lot of people used this product was because you could not schedule Process Builders.  Now that you can schedule Flows, I'd encourage you to just use Flows.

Write an answer...
0/9000
Shayna Stockton (Salesforce Admin at University of St Thomas)
Oct 3, 2025, 9:14 PM
Mass Action triggered in Sandbox running in Production?

We have a Mass action that is being run in staging to test some changes but I am getting flow error messages from Production. We have rolled our sandbox so the recordIds and input Id all match, and it seems like it is somehow trying to run in the wrong org? Has anyone else run into this? What can we do to stop it?

3 answers
  1. Shayna Stockton (University of St Thomas)
    Oct 6, 2025, 1:30 PM

    Issue found! The named credential in staging was still pointing to Production. I switched the actions to run as user in staging and it seems to be working. Looking now to see if I can change the credential but might need to set up a new one since it's trying to use the production User.

Write an answer...
0/9000
Christine (Chrissy) Priester (Salesforce Solutions Architect at Ascend Technologies)
Sep 18, 2025, 8:51 PM
Disabling Mass Action Log History Trigger

I am needing to mass delete roughly 2.5 million Mass Action Log History records and I keep running into an error that I suspect is due to the trigger on the Mass Action Log History object. Any ideas on any workarounds? I was thinking next steps would be to disable the trigger but I am not able to do that since it is a part of a managed package. 

2 answers
  1. Sai Akshitha Gaddam, Ph.D. (Archer-Daniels-Midland)
    Sep 18, 2025, 9:17 PM

    @Christine (Chrissy) Priester Since you can’t disable the trigger as it’s part of a managed package, the next steps really depend on the exact error you’re running into. Often the issue comes from record relationships, so you’ll need to clear those first — usually by deleting child records before parent records. After that, run the deletions in manageable batches to avoid limits and trigger errors.

Write an answer...
0/9000
Sambasiva Koidala (HCL)
Sep 9, 2025, 5:12 AM
One of the Mass Action Scheduler jobs is failing due to the Too Many Call Outs 101 error. How can we fix this issue.

One of the Mass Action Scheduler jobs is failing due to the Too Many Call Outs 101 error. How can we fix this issue.

4 answers
Write an answer...
0/9000
Yadira Avila Espinosa (Senior Salesforce Administrator at CELLCORE)
Aug 8, 2025, 1:43 PM
Hello, I have this package installed in my Org and stop working Yesterday, any idea what could be the reason?

I usually use this package for some Mass action scheduled in not business hours but, Yesterday, august 7, all stop working?

2 answers
  1. Utkarsh Gupta (Salesforce)
    Aug 11, 2025, 4:35 PM

    Hi, @Yadira Avila Espinosa Maybe the package is expired. You can check the status "Expired" or "Active" in "Installed packages" [Setup-> Search "Installed packages" in "Quick Find"]. Or, maybe somebody has removed a permission set that is part of the package from the affected users.

Write an answer...
0/9000
Janeé Williams (Associate Director, Operations at National Council for Community Education and Partnerships) asked in Salesforce Flow Automation
Aug 4, 2025, 3:10 PM
How do I get a flow to automatically expire opportunities after a certain date?

Hi All, 

I have opportunites that have member start/end dates fields. The opportunity status needs to be expired after the end date on the opportunity. I recently created a flow that will expire the opportunity after it's saved if the criteria was met. However, I'd like it to expire automatically without the record needing to be saved. How can I do this in flow successfully?I started an autolanuched flow but I'm not sure it'sthe right direction. Any help would be great! Pics below:  

How do I get a flow to automatically expire opportunities after a certain date?

 

 

Screenshot 2025-08-04 at 11.08.46 AM.png

 

 

Screenshot 2025-08-04 at 11.08.59 AM.png

 

 

5 answers
Write an answer...
0/9000
Ross Gilbert (Systems Operations Manager at AlertMedia)
Aug 4, 2025, 5:23 PM
Turning off process builders installed as part of this app

Someone long ago installed this package in my salesforce org.  It has two process builders in it that are active.  Since the package is managed I have no way of seeing what these 2 process builders even do.  And since this appears to be an some guy somewhere just put out into the world and not a real company, I cannot log a real support ticket. 

 

Does anyone have any idea if it would be safe for me to turn off the 2 active process builders I see that appear to be part of this app, wiithout breaking anything?  I think just looking at them they simply send some kind of email alert on some sort of failure(s) but I really have no way of knowing.  The process builders are called: 

 

MAS: Batch Apex Error Event 

MAS: Mass Action Configuration 

 

Thanks guys

1 answer
Write an answer...
0/9000
Gabriel Martins
Jun 19, 2025, 7:09 AM
An error occurred with your "MAS: Batch Apex Error Event" flow

Does anyone receive email notifications reporting the error with the managed flows from the FlowApplication lately? 

 

They are related to the two Processes MAS: Mass Action Configuration and MAS: Batch Apex Error Event, in Process Builder. We started receiving the error yesterday. It throws the error message every time the scheduled flows in the MAS run. Since they are managed processes in the package, we can't directly migrate them to the flow or deactivate them to stop the email notification, as now it's unlikely to reactivate the managed process in Process Builder after deactivation. Especially, keeping the MAS: Batch Apex Error Event flow active is compulsory to create the Mass Action Log. 

 

Does anyone know whether the issue could be related to the latest SF Summer '25 release? I wonder whether the processes are using the legacy REST API version that has been retired.  

https://help.salesforce.com/s/articleView?id=release-notes.rn_api_retirement_delay_256rn.htm&release=256&type=5

 

It would be very much appreciated if someone already had a solution to migrate or rebuild these two processes that can be shared in the community.   

An error occurred with your

 

 

An-error-occurred-with-your-MAS-Mass-Action-Configuration-flow-06-19-2025_02_43_PM.png

 

 

Write an answer...
0/9000
Tim May (Principal Software Architect at ScienceLogic, Inc.) asked in Salesforce Flow Automation
Feb 26, 2025, 4:32 PM
Limit the Batch Size for a Scheduled Flow

I've seen this a few other places around (reddit, stack exchange) and I'm curious if there is an answer to this. Scheduled Flows automatically break up the batching of records to make things very easy, which is good. However I'm running into an issue where the Einstein Case Classification action only wants to take in at most 50 records.  

 

The action gives this error: 

 

Error element Apply_Case_Classifications (FlowActionCall). 

This action can bulkify up to 50 case IDs at a time. If you're calling this action from a flow, make sure that you've configured a fault path to send a notification for this error.  

 

So there is definitely a Fault Path added to the Flow as requested, but I'm more worried that the Flow isn't running properly as I cannot control the number of records going into the Flow. 

 

I did find a feature in Winter '22 that I haven't yet used, but it is setting a batch size on a scheduled path.   

https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_scheduled_paths_minutes.htm&release=234&type=5

 

 

I'm trying to figure out how best to get the list of Cases into a scheduled path. I'm guessing I could do a small checkbox on the Case that is toggled on and off and this causes the Flow to do a scheduled path in batches of 50. Then after the Case is updated, uncheck the box. This is kinda messy though as it would be a Scheduled Flow to check a box and a second record-triggered Flow to run the ECC action in batches of 50 and then update the checkbox back to False. 

 

Anyone use the ECC action as a scheduled Flow?

1 answer
Write an answer...
0/9000