Trigger in managed package always hit Apex Cpu limit

Question

We implement Trigger Framework in our organization however we start buying apps that use trigger in managed package which we don't have control over it.Therefore I believe one trigger perobject is no longer applied because we have other triggers in managed package.

There is one apps that it always hit Apex CPU limit whenever we update data and current work around is to turn off that apps whenever we want to do bulk update.

I am thinking if there anyway that we can control the sequence like checking if the apps trigger is run, and if yes then we will not run our trigger so it can minimize the apex cpu limit exception.

I already apply bulkify in our org trigger , minimize the soql by using Maps etc. But I don't have control over trigger in managed package.

Have anyone face this issue before ?

Answer 1

If the other app is triggering the CPU limit, there's no way to determine if you'll be contributing to the problem ahead of time. Instead, you should probably contact the vendor to see if they have a mechanism to disable the logic through a utility class for bulk updates, or ask them to optimize their code. Alternatively, if it's not validation code, you might simply decide to use a Queueable instead of normal code so that you minimize your impact to CPU time.