Our Salesforce org depends on about 20 managed packages, many of which include their own SObjects, and many of those SObjects have their own trigger operations.
But we also need to do our own things with them, things which for a variety of reasons we want/need to do with triggers.
Unfortunately, SFDC does not offer us any native way to specify a sort order for trigger operations.
Even more vexing, neither do the third party vendors give us any way to inject our solutions into their trigger processes.
So, I'm wondering if there are any third party solutions / hacks which will allow us to control the order of operations?
Alternatively, if it is impossible to take complete control, what might be the pros and cons of using the Trigger just to launch an asynchronous event so we could guarantee our operation is last? Could we actually somehow guarantee at least that? Or could we find ourselves facing race conditions? And would there be any recommended solutions to avoid recursion / circular logic?