<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/discussions/f/rpa/40170/how-do-you-implement-a-try-catch-in-appian-rpa-no-code-environment</link><description>How do you implement a try/catch in Appian RPA no code environment? 
 Thank you.</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153492?ContentTypeID=1</link><pubDate>Wed, 11 Feb 2026 16:36:23 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:e4e60013-7d9f-449b-88c9-01e3b0f0635c</guid><dc:creator>Jesse Knight</dc:creator><description>&lt;p&gt;That&amp;#39;s not my point - see above, where I think there are great use cases for specifics on try/catch. My point is that it was never a great idea in software (even before RPA) to use try/catch as the only approach to error handling.&lt;/p&gt;
&lt;p&gt;As for whether RPA as a fundamental technology is even relevant these days.... in my personal opinion, it isn&amp;#39;t. But Appian doesn&amp;#39;t typically listen to my hot takes when determining what&amp;#39;s on their roadmap.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153489?ContentTypeID=1</link><pubDate>Wed, 11 Feb 2026 15:23:47 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:bf6b577f-ac1d-4bc6-8d1f-95f2166aaa68</guid><dc:creator>nicolaem159908</dc:creator><description>&lt;p&gt;&lt;a href="/members/jessek855119"&gt;Jesse Knight&lt;/a&gt;&amp;nbsp; - so your point is let&amp;#39;s not ask Appian to implement any other activities because we don&amp;#39;t need it (&amp;quot;pushing the problem off&amp;quot;). And also your point is UIPath RPA / Blue prism RPA / Automation Anywhere RPA ... they are not modern RPAs, top of the market systems ... they are all stupid guys that don&amp;#39;t know what they are talking about. Jessy ... really????&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153488?ContentTypeID=1</link><pubDate>Wed, 11 Feb 2026 15:19:34 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:1a865269-5fcb-4dab-9237-b68e0f73b3e5</guid><dc:creator>Jesse Knight</dc:creator><description>&lt;p&gt;Sure, re-throwing an Exception is a thing. But again, that simply means you&amp;#39;re pushing the problem off onto some other part of the code passively, rather than proactively dealing with it. In some cases, such as generic connection handlers, that makes sense. Yet in most cases it&amp;#39;s simply a way to punt on a problem that should be dealt with.&lt;/p&gt;
&lt;p&gt;The time / effort to handle an error will be spent at some point, whether it&amp;#39;s dealt with immediately via checks or rethrown and dealt with in a few months as a mess of data / processes that need to be cleaned up.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153486?ContentTypeID=1</link><pubDate>Wed, 11 Feb 2026 14:28:12 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:f864b954-147f-4e64-809f-e4e997537eaa</guid><dc:creator>nicolaem159908</dc:creator><description>&lt;p&gt;&lt;a href="/members/jessek855119"&gt;Jesse Knight&lt;/a&gt;&amp;nbsp;- sorry but I disagree and this is the reason why: a try/catch combined with a &amp;quot;throw&amp;quot; or a &amp;quot;rethrow&amp;quot; (to force the generation of an error) is a powerful way of directing the code to a specific part of the program that should run or not. That means control not &amp;quot;developer has not checked&amp;quot;. By the way, couldn&amp;#39;t find in this Appian RPA a &amp;quot;throw&amp;quot; (or a &amp;quot;rethrow&amp;quot;) activity but again, the number of things that are missing ... I don&amp;#39;t really want to talk about it because is very frustrating.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153485?ContentTypeID=1</link><pubDate>Wed, 11 Feb 2026 14:17:32 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:47efb9ea-49a2-41ee-b4d5-fa10adf4d1ca</guid><dc:creator>Jesse Knight</dc:creator><description>&lt;p&gt;I disagree that a &amp;#39;catch&amp;#39; block is &amp;#39;powerful&amp;#39; in the longer term. Most of the time they are a &amp;#39;code smell&amp;#39; because they imply that a developer has not checked the assumptions about initial conditions / data in their code prior to running it. The reality of nearly all code I&amp;#39;ve written and reviewed is that a&amp;nbsp;&amp;#39;catch&amp;#39; block is just a way for developers to ignore problems by logging them to deal with later. Sometimes that is all that can be done (e.g. leaky abstractions, where a lower-level library throws a generic exception with no relevant means of handling it in a specific way), but most other times it is far more performant and maintainable to check assumptions ahead of the try() block.&lt;/p&gt;
&lt;p&gt;The lack of generic error-handling in Appian, while absolutely frustrating at times in early development, is a way to force developers to properly address errors in their code as part of productionization. I do wish Appian would formally support try/catch (specifically to gracefully handle issues with data-driven dropdowns), but I also know developers would simply abuse it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153478?ContentTypeID=1</link><pubDate>Tue, 10 Feb 2026 17:24:29 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:e8576a18-b1da-4bf0-bee3-659eb45d5ed8</guid><dc:creator>miguelangel.carnero</dc:creator><description>&lt;p&gt;Thanks for raising this. You&amp;#39;re right that try/catch is common practice in RPA tools. We hear you and understand the desire for robust error handling in RPA, and we&amp;#39;re actively working to enhance this area.&lt;/p&gt;
&lt;p&gt;While Appian RPA is designed to integrate legacy systems into the broader Appian platform (where you can leverage process models for complex logic and error handling), we recognize that native try/catch capabilities in RPA would make certain workflows more efficient.&lt;/p&gt;
&lt;p&gt;This capability is on our roadmap, and we&amp;#39;re evaluating the best approach to deliver it in a way that fits naturally with Appian&amp;#39;s unified platform. We appreciate this kind of direct feedback, as it helps us prioritize what matters most to our customers.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153462?ContentTypeID=1</link><pubDate>Mon, 09 Feb 2026 15:57:50 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:3785e348-a301-46ef-bafe-27fc87f29e03</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;&amp;nbsp;&lt;a href="https://community.appian.com/betas/b/programs/posts/agentic-ai-rpa"&gt;Agentic RPA&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153461?ContentTypeID=1</link><pubDate>Mon, 09 Feb 2026 15:39:35 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ad1ec877-2144-46cf-ac77-40df0dcf6b89</guid><dc:creator>nicolaem159908</dc:creator><description>&lt;p&gt;&lt;a href="/members/stefanhelzle0001"&gt;Stefan Helzle&lt;/a&gt;&amp;nbsp;- you are so right!!! The question is why there is no progress on this bandaid from Appian? any Appian employees here?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153460?ContentTypeID=1</link><pubDate>Mon, 09 Feb 2026 15:35:12 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:f8265ea0-480d-4366-92f0-aa95bdb8767d</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;Think of Appian RPA as a bandaid to integrate a legacy system. Use standard Appian processes for the more complex logic.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153459?ContentTypeID=1</link><pubDate>Mon, 09 Feb 2026 15:20:05 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:379dc279-72f8-4f7c-ac71-98c8cc6c23df</guid><dc:creator>nicolaem159908</dc:creator><description>&lt;p&gt;&lt;a href="/members/shubhama926776"&gt;Shubham Aware&lt;/a&gt;&amp;nbsp;- yup, I was aware of this &amp;quot;go around&amp;quot; techniques. I was hopping for something more powerful, something that&amp;nbsp;modern RPAs (UIPath RPA/Blue Prism RPA/Automation Anywhere RPA)&amp;nbsp;have.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153458?ContentTypeID=1</link><pubDate>Mon, 09 Feb 2026 15:17:20 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:03168336-9066-429e-a311-73628f72899e</guid><dc:creator>nicolaem159908</dc:creator><description>&lt;p&gt;&amp;nbsp;&lt;a href="/members/stefanhelzle0001"&gt;Stefan Helzle&lt;/a&gt;&amp;nbsp;- use&amp;nbsp;the &amp;quot;try&amp;quot; to find the error and based on the type of the error to do something in the &amp;quot;catch&amp;quot; section. Similar to what modern RPAs (UIPath RPA/Blue Prism RPA/Automation Anywhere RPA) are able to implement.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153450?ContentTypeID=1</link><pubDate>Sat, 07 Feb 2026 08:03:11 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:403e020c-6b4e-4687-a386-9f8a37e3b7ce</guid><dc:creator>Shubham Aware</dc:creator><description>&lt;p&gt;Use conditional blocks (Element exists?, Window exists?, return codes) to branch flow: success path = try, failure path = catch.&lt;br /&gt;For task failures, handle in calling process model via Execute Robotic Task&amp;#39;s error outputs (status, message).​&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Better to go through this documented links:&lt;br /&gt;&lt;a href="https://docs.appian.com/suite/help/26.1/rpa-9.17/design-patterns.html"&gt;https://docs.appian.com/suite/help/26.1/rpa-9.17/design-patterns.html&lt;br /&gt;&lt;br /&gt;&lt;/a&gt;&lt;a href="/success/w/guide/3289/appian-rpa-design-development-best-practices"&gt;https://community.appian.com/success/w/guide/3289/appian-rpa-design-development-best-practices&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How do you implement a try/catch in Appian RPA no code environment?</title><link>https://community.appian.com/thread/153449?ContentTypeID=1</link><pubDate>Sat, 07 Feb 2026 07:49:47 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:44f9f249-efd0-48e4-af25-2604851b7750</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;There is no direct implementation of a try/catch in Appian RPA, just like there is not in Appian expressions.&lt;/p&gt;
&lt;p&gt;But, what problem do you try to solve?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>