Yeah, that would be useful. So, if a trigger fails to execute because of conditions, I guess it wouldn't get updated even though the initial event was received? I guess the question is: lastExecuted or lastFired?
BTW, we don't currently store that data so unfortunately it's not just a client fix...
I was thinking Fired, not executed, but both would be good. Now for extra credit, a note or something about which condition caused the execute failure....
I was thinking Fired, not executed, but both would be good. Now for extra credit, a note or something about which condition caused the execute failure....
That one's gonna have to wait until we revisit the entire trigger/schedule flow (which will allow actions to know about where they're executed from). It's not really even scheduled at this time because the work is so pervasive.