Create and execute jobs fails the first time after server startup

[armingrudd]

To those who may encounter the same issue:
There is a workaround to make the node be re-executed after the failure:

Re-execute on error

Hi David, I think I have found a method to do what you need: [re-execute] In this example workflow I have a Get Request node which may produce an error while executing (for example when there is no connection if you check the option in the configuration window). I could loop over the nodes until they executed successfully and I got what I wanted (in this case a list of countries). I used a “Generic Loop Start” and “Try” before the main nodes (no configuration) and after the main nodes used…