In the library, all triggers are assigned a StartBoundary when constructed. It appears, now that you bring this to my attention, that the native library only assigns a StartBoundary to calendar triggers by default. Is this a problem for your code? I can't see any scenario where having a StartBoundary set to a time in the past would cause any different behavior.
↧