Hi NTillinghast,
We had a similar issue - it's not obvious at all in the Sisense UI, but if you schedule a cube to refresh eg. every 2 hours and 30 minutes, that actually means it will refresh every 2 minutes at 30 minutes past the hour. We used this to shift a lot of our cube refreshes to at 30 minutes past the hour, and schedule a few particularly beefy ones at specific times.
From your link:
IMPORTANT: Setting the days/hours/minutes of an interval will run a build at the specified days/hours/minutes - not every X days/hours/minutes. For example: 1 hour 30 minutes does not mean every 90 minutes; it means every hour at 30 minutes past the hour.
If a build fails, Sisense waits until the next interval to run the build again.
Give it a go!
