Is this an anti-pattern? The desired effect is to respond to a deadline by issuing commands or applying events that contain data that may have been updated during the interim. In an aggregate this would be performed in a command handler, while in a saga it would be performed in an event handler. The data could be an axon-driven view, or some other outside I/O. It seems reasonable enough, but I am not certain of the implications on task management and unit-of-work.