<?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>Activity Chaining - The amount of time between attended tasks exceeds the non-configurable limit of 10 minutes.</title><link>https://community.appian.com/discussions/f/best-practices/35063/activity-chaining---the-amount-of-time-between-attended-tasks-exceeds-the-non-configurable-limit-of-10-minutes</link><description>Hi Community, 
 Was going through documentation for breaking-a-chain and came across this point The amount of time between attended tasks exceeds the non-configurable limit of 10 minutes. 
 Can anyone explain this pointer with example? 
 
 What do we</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Activity Chaining - The amount of time between attended tasks exceeds the non-configurable limit of 10 minutes.</title><link>https://community.appian.com/thread/135774?ContentTypeID=1</link><pubDate>Thu, 23 May 2024 16:18:09 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:7f5eb3a6-bc91-4e30-afe9-37c2ca72fd5d</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;This is sort of a basic principle of Appian process models... but for clarity, an Attended Task is essentially anything that halts the process flow to wait for user input.&amp;nbsp; Apart from rare exceptions, this is almost always a User Input Task node (there are some other types that can have a form added, but this is rarely done and, IMHO, should be avoided).&lt;/p&gt;
&lt;p&gt;You&amp;#39;d almost never encounter any condition when chaining tries to persist for that length of time and isn&amp;#39;t broken anyway.&amp;nbsp; Certain node types (timers, rules, etc) automatically cause chaining to stop when encountered - so something that takes that length of time would be, for instance, a very load-intensive smart service node (document generation, or some other type thing that could take excessive amounts of time).&amp;nbsp; Generally this would be designed around, because from the user perspective, they&amp;#39;d be sitting there just looking at a loading screen when waiting on long-running process elements like that to complete, which is a horrible design.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>