this episode is brought to you by sacon which is on my list of apps with the most potential for game-changing savings talk to your organization's mobility manager and they'll tell you the nightmare of managing multiple carriers per country each with their own offerings contracts and integrations sake sakon abstracts and manages this for you eliminating the swivel chair mobility management work and giving you asset and configuration data you can trust sakon is mobility managed check the description below okay quick editor's note here in the upcoming video i keep referring to this feature as try catch and while it has several similarities to the coding principle of try catch i'm not sure if it's an exact match or not and servicenow only calls it the try method so every time you hear me say try catch just here try hey everyone welcome to a servicenow san diego essentials it is so good to have you here in this video we are talking about try catch in flow design and before we get started i just like to do a little shout out to andrew barnes and john dahl who helped me flesh out some of my knowledge to prepare this video try catch is an awesome new addition to flow logic which helps your flows be a lot more flexible when it comes to failures errors and edge cases it's different from both if statements and out of box error handling for flows and we'll show you just how different via an example now we're going to imagine a scenario where they want to update client of an incident via sms if the priority changes because email isn't annoying enough so here's our action to send the sms and here's our action to update the work notes to say that we sent the sms and then because we're good stewards of our flow we're gonna log an entry if this flow fails in any way so we're gonna test this incident but what you don't know is that the customer of that incident doesn't even have a number with which to sms let's run the test the test is successful but the output is very interesting as you can see the flow stopped right here no more flow for you and since it failed it's discontinued the flow and launched the error handling actions okay let's compare this to a flow that's using the new try catch flow logic when you put a try catching your flow you get these two pathways this is the part that makes it different from an if statement because it is not evaluating anything in that first pathway it just assumes that it must do it when the try block can't be run for whatever reason the catch block will always run always there's no stopping the flow can't stop this baby so again knowing that this is for a user that we can't sms let's take a look at the output for this flow we're picking the same incident to test with running the test in this case we see that the try pathway failed it could not send an sms message to the user so what did it do it went through the catch block and executed the instructions there and fully completed the flow and if that's not cool enough you can add multiple tri-catches to your flow either in line or nested within each other so the main thing you need to know is with tri-catch flow logic it will always fail into the catch this is one of my favorite san diego features as it allows flows to better contend with reality which sometimes has exceptions and failures and it takes a complicated pro code concept like try catch and makes it accessible to citizen developers thanks for watching we'll see you on the next one if you're a servicenow expert looking for better opportunities but maybe your resume or linkedin profile isn't doing you justice reach out to me via linkedin or the email pictured here as i offer both career coaching and recruitment services and if you're a servicenow customer or partner you heard that right robert fedoric now does servicenow recruiting with a 1500 subscriber youtube channel and mailing list and thousands of linkedin followers let's make sure your open positions get first go with the prodigious pool of servicenow resources reach out via the emailed picture here