When using Every Elasticube Update send option send when final elasticube is processed not the first

It may be challenging since Sisense doesn't really have a way to know (today) that it is processing 1 cube out of 5.  I.e. there's no logical chain of cubes, other than by schedule.

Maybe a quick-and-dirty implementation of this is a field that lets you specify, "do not send notification before [00:00]" and the user can pick a time.  That way they could time it roughly near when the last cube build completes.

A more comprehensive solution would be to let you schedule a chain/sequence of cubes rather than simply cube-by-cube.  This would also let you decrease the total time it takes, since you don't have to have any buffer time built into each cube's schedule.