I have several custom fields on the Account object that serve as rollup counts of specific Activities, e.g. Open Task Count, Completed Task Count, etc. I fill these fields via an after trigger on the Task object that involves an update of the parent Account. All works great, ok.
Now for a separate project, I have been tasked with creating a trigger on the Account object that creates a task (within that account) under certain circumstances. This runs into a recursive self-update issue — if the Account trigger creates a Task, the Task trigger then tries to update the Account and of course this is not allowed.
I am aware of the Trigger Pattern for Tidy, Streamlined, Bulkified Triggers, which I can see is very nice but I am honestly just not at the skill level to implement it, nor do I have that kind of bandwidth to learn it at the moment.
So, barring a total re-architecting of my entire org's trigger setup, is there a quicker way to work around this issue?