Commit detection adjustment in triggers. (Identity key and lasting duration of detection)


I’m writing a custom trigger and i was wondering if we can do the following customization to make my script more dynamic and volatile.

1. To be able to adjust the identity key of the commit detection function to whatever duration i want.
Current default timing of 1 hour is too short, while 1 day is too long.

2. To commit detection only when there is the detection condition and the timeframe of it is lasting for at least 6 hours.
Can’t seems to find a way to do such granular filtering.

Many thanks in advance!

Hi @bryanteocw! responses inline below.

hour, day, and week are the only options.

You might be able to accomplish something like this using longer-cycle metrics, assuming there is a corresponding metric to the activity in question.