Turns our there is a "hidden" and undocumented scenario catch-up fuctionality built-in into Dataiku. You can read about it here. This Idea is to be able to have control over this hidden scenario catch-up fuctionality. In particular we would like to Disable the scenario catch-up fuctionality so that Dataiku Scenarios do not run outside their pre-defined schedules after DSS has been shutdown for maintenance. We would also like it not to run when the disableAutomaticTriggers setting gets set to False and whatever other situations Dataiku will invoke this functionality. Basically we want to have full control on when things run and if the DSS instance was shutdown or disableAutomaticTriggers setting enabled it should not run scenarios with time-based triggers which were missed.