What is the preferred design pattern to ensure entity properties are always in sync with issues

kirksl March 23, 2018
I have an add on that has an issue changed webhook. Everytime an issue is changed I update the specific issues entity properties too ensure its set and current.

I need to ensure all issues have an entity property set and that it is current all the time.

What is the best approach to guarantee this?

I'm thinking about situations if the add on ever goes down and things can get out of sync too.

Should I store a global last updated property somewhere and check it on regular frequency based on another web hook? Or on a timer? And batch check update all issues changed after the last updated date I stored?

0 answers

Suggest an answer

Log in or Sign up to answer