Flow designer vs Scheduled Job

rajeeshraj
Tera Guru

What best-practice guidelines should be used to decide between Flow Designer and a scheduled job—such as transaction volume, payload size, event queue impact, or similar factors?

 

Thanks

9 REPLIES 9

Tanushree Maiti
Kilo Patron

Hi @rajeeshraj 

 

It is based on your use cases.

 

Flow Designer is the recommended default for new automation due to its maintainability, auditability, and ease of use,

while Scheduled Jobs (Scheduled Scripts) should be reserved for high-volume, performance-sensitive, or highly complex scripting scenarios.

 

Note : If you have already created a long-running flow, then recommendation is using a Scheduled Script to trigger the flow on demand.

The function below allows you to execute the flow on demand using the “Execute Now” option in the Scheduled Script: 

sn_fd.FlowAPI.startFlow();

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

rajeeshraj
Tera Guru

Thanks, I’m looking for criteria like these. What would be considered high volume when choosing a scheduled job? For example, more than 10k records processed?

Also, how do we define performance in this context? Is it based on the amount of data processed, the complexity of the logic involved, or something else?

SohamTipnis
Mega Sage

Hi @rajeeshraj,

 

There’s no strict rule from ServiceNow, but in practice the decision comes down to how heavy and how frequent your processing is.

If your use case is event-based, real-time, and not too heavy, Flow Designer is the better choice. It’s easier to maintain, more readable, and works well for approvals, notifications, and integrations triggered by record changes.

But if you’re dealing with large volumes of data, heavy loops, or scheduled batch processing (like thousands of records at once), then a scheduled job is preferred. It gives you better performance control and avoids overloading the Flow Engine or event queue.

So in simple terms:
👉 Use Flow Designer for business processes and real-time automation
👉 Use Scheduled Jobs for bulk processing and performance-heavy tasks

 

Let me know if this works!!!!😀

 

 

If you find my answer useful, please mark it as Helpful and Correct. ‌‌‌‌‌‌‌‌‌😊


Regards,
Soham Tipnis
ServiceNow Developer ||  Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10

shubhamseth
Mega Sage

@rajeeshraj Trying to make it very short yet meaningful insights: 

 

Flow Designer: Best for ASYNC, Event driven orchestration where logic is modular, human readable format, and loosely coupled. 

 

Scheduled Jobs: Best for high batch execution where you need low level control over queires, memory and execution time without flow runtime overhead. 

 

Rule of thumb: 

if it needs orchestration - Go for Flow Designer 

If it needs performance at scale - Go for Schedule Job

 

 

✔️ If this solves your issue, please mark it as Correct.


✔️ If you found it helpful, please mark it as Helpful.



Shubham Jain