Hi all, so I’m attempting to handle the scenario in which my app cannot send a mail (for whatever reason, let’s assume the network is down). The mail step happens after I create a new user (I then subsequently do a query to get all of the new user’s info and not just the identity from the insert step).
In the catch step for the Send Mail action, I’m attempting to delete the user if the mail failed to send, however, it doesn’t seem to be working…the new user is created but never removed and no errors are thrown in the browser.
Oh, interesting. I’ll investigate and report back. That makes sense since it tries to establish a connection prior to sending the mail and that’s the step that fails.
Okay, so if I move the Setup Mailer step into the repeater before the Send Mail action, like before, the browser no longer throws an error (not sure why this is the case now and in my first post), but the user is not removed.
If I leave the Setup Mailer step where it was and try to place the delete action in the catch block at the top level, I’m not sure how I can get a reference to the id of the created user to remove…
I wasn’t aware of this, tried it and still no luck. As you can see in my previous screenshots, I didn’t need to specify the output fields in order to bind to the exposed record’s properties, they were all just listed in the dynamic data picker.
The output is required only for the front end - when you want to make these available on your pages, on the server side it doesn’t make any difference, i.e. you can access the properties without enabling output.
I will test this locally and will let you know what’s wrong.
In your second screenshot, what step failed to throw the exception with the Set Value? Also, do exceptions bubble up (inner exception bubbles up to outer catch block)?
Hard to know if the catch block is running as I’m calling this action from a server connect form (I don’t have a Server Connect component in my App Structure). Should I be doing something different?
