Web get error in flow should not terminate entire process

Ideas
1

Currently, if any web get error occurs in flow, the entire flow stops. This isn’t ideal in case I want to handle such errors gracefully. For my use case, an API call may result in a 404. I want to detect this error and perform a different process.

I am unable to accomplish this efficiently when the flow stops and my previous data is still stored in the global. It would also help me if there could be a local variable #error set when these webget issues happen.

1 Like
2

Good point, will add “continue on failure” into 3.80, webget will also set a special local var called #code with the response code, i need to add an example for this somewhere.