Flow designer vs Scheduled Job
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
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
- Labels:
-
Flow Designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago - last edited 3 hours ago
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:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
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?
