Hello,
I have created a time condition for a step “Wait for a condition”. Normally, the formula compares the time NOW with the time the last row was created. After 1 minute, the expression should be TRUE and the next step should be triggered . I have used this kind of condition as action filter in behavior field before and it worked good, but in automation seems not to be working. I have tested it in the expression builder and it gave me the value I was expecting.
Thanks Dan for your fast answer! I got it: the row needs to be updated for the condition to be evaluated.
As an answer to your question “Would have a step that can wait a given amount of time be desirable for your use cases ?” For me this feature would be helpfull. Lots of times I try to implement some time conditions, for example:
If you always perform some behaviour at same time, you can just schedule a report, BUT sometimes I cannot have a fixed time everyday to do some stuff. Examples:
-In my country work break must last at least 15 minutes by law, so the action to finish break time should only be visible 15 minutes after the beginning of break (to avoid people registering shorter breaks).
-Same with some tasks: they need to be performed at certain times, but starting time varies depending on when you started working that day. By showing and hiding actions depending on relative times, I can avoid mistakes when clicking on wrong actions. These are “fake” data inputs I prefer to avoid.
I too would find it beneficial to have a step that can wait a set amount of time. If I dont have this, I WILL make 6-18 scheduled automations/workflows that do the exact thing (check if created time of row is X hours ago).
Use case: In a deployed Timelogs app, I have users (and their supervisors) asking me to create an “auto-notice” to remind them about their active log after 2 hours (and preferably also after 4 hrs, 6 hrs, etc).
I have several other ideas where a delayed-notification like so would be very handy, possibly days after (new contact not yet contacted, invoice not yet sent out, etc). Such things would be quite bulky and frankly ugly to create with the current features available.
We are planning to release a new feature on the wait step where you can control the timeout behavior.
The Wait step type allows the process to pause execution and before resuming:
[Wait for a condition] to evaluate to TRUE or a timeout period to be reached
And here you can add steps in case the timeout period has been reached
Note: Process execution will not resume at the exact time that time period is met. There may be a delay of up to 10 minutes. Therefore, the Wait step does not support use cases where accurate timing is required.
Would you be interested in getting early access? If yes, just let me know your appsheet user id. @Ferret and @Dani_Mi as well.
