https://community.appian.com/discussions/f/general/17203/timeout-in-a-webapi-wich-use-startprocessHi! I wanted to know how many seconds must pass before startprocess called by a webApi breaks by timeout. We know that it can be used until 50 nodes in a process called by a webApi but not the waiting time. Regards, Rebecaen-USTelligent Community 12https://community.appian.com/thread/68051?ContentTypeID=1Tue, 09 Jul 2019 09:02:14 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:cf818c27-3725-4856-accb-efd47de6dc2erebecar369<p>Thanks</p><div style="clear:both;"></div>https://community.appian.com/thread/68044?ContentTypeID=1Mon, 08 Jul 2019 22:41:40 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:28cc4712-dfc4-44aa-b2b6-05508d01ec39Tom<p>Hi Rebeca,</p> <p>According to the &quot;Breaking a Chain&quot; section on the&nbsp;<a href="https://docs.appian.com/suite/help/19.2/Process_Model_Recipes.html#using-activity-chaining-to-display-multiple-forms-in-succession">&quot;Common Process Model Workflows and Recipes&quot;</a>, the time it takes for an Activity Chain to break is ten minutes per node join. As such, as long as the process model linked via a!startProcess is activity chained, I can&#39;t see a case this would ever exceed and break. Even if it were to exceed, the a!startProcess would finish and execute its &quot;onSuccess&quot; content, meaning that you should get a response still (albeit without some of the data).</p> <p>As such, it appears to imply that any timeouts would be subject to the caller of the WebAPI rather than the WebAPI itself as Appian would be actively working. For instance, for a response time that large, it may be hard to justify using it as a link on a web page, but it may be okay as a REST API.</p> <p>Kind Regards,<br />Tom</p><div style="clear:both;"></div>