Automation Timers - ensuring predictability / removing edge cases

1 Comments

  • Nathan Purcell

    Mitch has done a great job of explaining my use-case also. The "greater than" option is causing problems and the additional hour has been experienced multiple times. 

    A bit of transparency of when in the hour our automations are due to run would help. Perhaps being able to link/chain automations (Run B only once A has completed). 

    Finally, testing is a painfully slow process as I am not aware of any way to work in a unit smaller than one hour. This is made worse given the scenario above with chained automations actually running at 2 hour intervals. If something is not correct I have potentially a three hour wait time for a 2 step process. 

    2

Please sign in to leave a comment.

Powered by Zendesk