Today this scheduler exists where a time slot can be chosen. In my company we have multiple teams working with redash and it’s hard to know when is a good time to schedule our query to not collide with existing queries and load the database too much.

A small fix idea is to have a number of the number of already scheduled queries for that specific time slot to indicate when there is a gap.

Another idea could be to use historic query-time data for the last three 24-hour periods of when the database was idle to display credible gaps of when to run.