#CPU Limit0 utenti parlano di questo argomento

Hello Laura, 

That CPU time limit error you're getting while updating the Kanban Board in Agile Accelerator is likely due to the managed package running too much Apex behind the scenes when saving the changes. Since it's a managed package, there's not much you can tweak directly in the code, but you can try a few workarounds. Try doing the update in an incognito window or a different browser to avoid any caching issues. Also, see if you can temporarily reduce the number of records or columns on the board — that can ease the processing load. Some users have had better luck by cloning the board and then making edits to the cloned version. If you’ve got any custom automation on Work or Status objects, try disabling it just while you make the update. And since you were successful after a few tries in the sandbox, trying again during off-peak hours might help. If all else fails, ask Salesforce to escalate it to the Agile Accelerator team — they might be able to suggest a fix or workaround.

Hi Kristan, That's Great that you got to learn best practices. For sure FLOWs is a very powerful automation tool on the force.com platform. But we have to be sure that there are still many use cases that we cannot achieve through Flows. There are some drawbacks and a lot of scope of improvments and I am sure Salesforce will come up with new features. I personally have seen a lot of changes on FLOWs.  

To answer your question: Before having a Trigger's feature in FLOWs we use it to invoke FLOWs through Process Builder.  This way you can still invoke multiple Flows on one object. But it will always be On-Creation or On-Edit of a record.