Search is a pain to remember the attempts and delays

[z1pti3]

I also noticed how much of a pain playbook is now you have to keep defining these on the search actions as well as the start action - we need to find a nicer more user friendly way to do this. I expect we need to include it in the playbook data and then when you change the values it does a mass update on the database for all existing playbook entries by x name

[z1pti3]

Why dont we have an option to load from an existing object?

[b1scuit-thi3f]

That would make sense, so it loads the maxAttempts and delayBetweenAttempts from the object instead? I guess we'd have to let it poll the object when it runs in the flow to maybe make sure the values were still accurate?

[z1pti3]

If we poll it as part of the init loading then jimi will cache the value until he rebuilds the trigger which by default is every 60 seconds.