Currently, the EdgeTemporalConstraintsScheduledService and the VertexTemporalConstraintsScheduledService will be invoked by the scheduler jobs scheduled at temporal constraint inception and expiration for temporal constraints on edges and vertices. These ScheduledService instances will dispatch the relationshipNotification 'signals' to the vertices affected by the temporal constraint inception/expiration. Note however, that this invocation dispatch is not robust - a failure will only be logged. There is no REST invocation to propagate the failure exception to, as these invocations are ultimately dispatched by a scheduled job. It might, however, make sense to determine a means to retry these failed invocations, as temporal constraint inception/expiration may well result in the provisioning of roles and the corresponding assignments.