Performance Issue with Flow After Yokohama Upgrade – Slow 'For Each' Step
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2025 12:39 AM
After upgrading to the Yokohama version, I encountered a significant slowdown when executing a particular flow for the first time.
In this flow, I use a "Look Up Records" step with Max Results set to 100,000, followed by a "For Each" step, and it seems the performance issue occurs especially during the "For Each" processing.
If possible, I would like to improve the performance without changing the logic of the flow, by adjusting only the configuration or settings.
If anyone knows of best practices or recommended settings for this scenario, your advice would be greatly appreciated.
Also, if you have experienced a similar issue after upgrading to the Yokohama version, we’d be grateful if you could share your experience as well. (I'm trying to determine whether the issue is related to the upgrade.)
Thank you in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
I thought I was experiencing this issue but I upgraded to another higher version of Yokohama patch13-hotfix4 but really what it was the system taking 24-48hrs to finish running all the system jobs and rebuild the cache with the new schema and tables. I didn't change system properties in Prod, just talked to Support and it was fine on the 3rd day. KB0756493 or KB2667024
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
57m ago
Our Prod and QA environment are better now. I forget to fix the try in Dev because our Dev is slow always.
But it's getting to the point on-prem DEV that it's an issue. so I adjusted that Collect Stats job in Dev to only run every 30 days like I did in Prod and QA- starting tonight
