Skip to main content
Salesforce

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 1
    This might be soluble in a Flow, but the solution is much cleaner and more scalable by using Batch Apex. Is that an option? Commented Jun 12, 2019 at 20:28
  • If this is a one time thing and you don't have apex skills, you could break it down further by considering only Accounts created in current year, then rerun for accounts created in prior year, etc. (or similar date filtering approach, perhaps on Oppos) Commented Jun 12, 2019 at 20:54
  • @DavidReed I agree that Batch Apex would be better, but my client has refused to use any code. I tried adding the "update opp" step to my original flow, but I still got the same error. Do you know how I could add this to a flow and make it work? Commented Jun 13, 2019 at 14:19
  • @cropredy I tried adding the "update opp" task to my original flow and just updated one Tier at a time, hoping that would break things into small enough chunks, but I got the same error. Commented Jun 13, 2019 at 14:19
  • 2
    Rochelle. Fundamentally, the flow is doing too much work per transaction and you need to reduce this. The CPU limit is fixed. You could always resort to Data Loader. Or look at the data and see if some Account(s) have a skewed amount of Oppos to update as that could be the issue (an outlier). The debug log can assist. Commented Jun 13, 2019 at 14:35