Closed chuck-dbos closed 3 months ago
Random thought: we need the exactly-once behavior in production, but it could be problematic in a dev environment. Might we want a flag that turns it on?
Sure, I think it makes sense to use current time and not consult the system DB as an option. Where would you put this option? In the config file? In the @scheduled config object? Elsewhere? (I could see doing both of these).
The configuration file makes the most sense to me.
Thanks! I like the current implementation. A nit is that registrationObject
is no longer used anywhere in workflow config. Can we remove it for now? We can think about refactoring in a separate PR.
Sure, I think it makes sense to use current time and not consult the system DB as an option. Where would you put this option? In the config file? In the @Scheduled config object? Elsewhere? (I could see doing both of these).