@stocksy Wow, I'm not sure how we missed that command ... and it looks like it fixes most of our retrying problems! 
It seems it doesn't work for all the resources though? That definitely fixes it for the file resource, but I tried to have a service() resource as well (which was checking that the "initialization service" that is setting up the files was indeed running) and it didn't detect that that service went from "not running"é to "running".
Do you know if it's considered as a bug and/or missing implementation for some resources?