<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RE: Log-in retry logic in University Forum</title>
    <link>https://community.blueprism.com/t5/University-Forum/Log-in-retry-logic/m-p/85136#M1518</link>
    <description>Hi Sam,&lt;BR /&gt;&lt;BR /&gt;Ideally speaking the login logic should not be retried but if in case you are retrying it make sure that you do not retry it for those many times which can risk you account to get locked.&lt;BR /&gt;&lt;BR /&gt;For example, in many web applications if let say you forgot your password or if you mistyped the password you still can attempt for 2 times but if for the third time you also do the same, your account might get locked out. It happens a lot while we do Net Banking doesn't it ! Even for a bot if the response time for a web application is too slow or too fast, it might enter the password incorrectly at times, hence retrying can be considered if not totally eliminated but then again in must be done in a controlled manner and with respect to keeping the application interface in mind.&lt;BR /&gt;&lt;BR /&gt;So similarly in your automation as well, the retry attempts can be there but it should not be retrying for that many times that can risk your account getting locked. We usually retry only for 2 times in case of login retries whereas for other retries we keep the attempt count to 3. &lt;BR /&gt;&lt;BR /&gt;Again, these attempt counts are decided based upon the organisation standards and the application infrastructure as well so there is no definite answer like for every case how many times you should ideally be retrying or not.&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;----------------------------------&lt;BR /&gt;Hope it helps you out and if my solution resolves your query, then please mark it as the 'Best Answer' so that the others members in the community having similar problem statement can track the answer easily in future&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Devneet Mohanty&lt;BR /&gt;Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,&lt;BR /&gt;Wonderbotz India Pvt. Ltd.&lt;BR /&gt;Blue Prism Community MVP | Blue Prism 7x Certified Professional&lt;BR /&gt;Website: &lt;A href="https://devneet.github.io/" target="test_blank"&gt;https://devneet.github.io/&lt;/A&gt;&lt;BR /&gt;Email: devneetmohanty07@gmail.com&lt;BR /&gt;&lt;BR /&gt;----------------------------------&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Wed, 11 May 2022 07:19:00 GMT</pubDate>
    <dc:creator>devneetmohanty07</dc:creator>
    <dc:date>2022-05-11T07:19:00Z</dc:date>
    <item>
      <title>Log-in retry logic</title>
      <link>https://community.blueprism.com/t5/University-Forum/Log-in-retry-logic/m-p/85134#M1516</link>
      <description>were mentioned in best practice that we don't retry Log-in action if there were any error occurred, the template does not even write an expression to retry only system exception, Could anyone explain why this has been done in BP Travel solution?&lt;BR /&gt;
&lt;DIV class="media" style="overflow: hidden; zoom: 1;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="32780.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/32878iA6EEAC32F8666A06/image-size/large?v=v2&amp;amp;px=999" role="button" title="32780.png" alt="32780.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV style="position: absolute; display: none; z-index: 16777271;"&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Sam Lima&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Tue, 10 May 2022 17:57:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/University-Forum/Log-in-retry-logic/m-p/85134#M1516</guid>
      <dc:creator>SamLima</dc:creator>
      <dc:date>2022-05-10T17:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: Log-in retry logic</title>
      <link>https://community.blueprism.com/t5/University-Forum/Log-in-retry-logic/m-p/85135#M1517</link>
      <description>&lt;P&gt;Could you please help me with this?&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/1843"&gt;@devneetmohanty07&lt;/a&gt;​&lt;/P&gt;
​&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Sam Lima&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Tue, 10 May 2022 18:36:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/University-Forum/Log-in-retry-logic/m-p/85135#M1517</guid>
      <dc:creator>SamLima</dc:creator>
      <dc:date>2022-05-10T18:36:00Z</dc:date>
    </item>
    <item>
      <title>RE: Log-in retry logic</title>
      <link>https://community.blueprism.com/t5/University-Forum/Log-in-retry-logic/m-p/85136#M1518</link>
      <description>Hi Sam,&lt;BR /&gt;&lt;BR /&gt;Ideally speaking the login logic should not be retried but if in case you are retrying it make sure that you do not retry it for those many times which can risk you account to get locked.&lt;BR /&gt;&lt;BR /&gt;For example, in many web applications if let say you forgot your password or if you mistyped the password you still can attempt for 2 times but if for the third time you also do the same, your account might get locked out. It happens a lot while we do Net Banking doesn't it ! Even for a bot if the response time for a web application is too slow or too fast, it might enter the password incorrectly at times, hence retrying can be considered if not totally eliminated but then again in must be done in a controlled manner and with respect to keeping the application interface in mind.&lt;BR /&gt;&lt;BR /&gt;So similarly in your automation as well, the retry attempts can be there but it should not be retrying for that many times that can risk your account getting locked. We usually retry only for 2 times in case of login retries whereas for other retries we keep the attempt count to 3. &lt;BR /&gt;&lt;BR /&gt;Again, these attempt counts are decided based upon the organisation standards and the application infrastructure as well so there is no definite answer like for every case how many times you should ideally be retrying or not.&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;----------------------------------&lt;BR /&gt;Hope it helps you out and if my solution resolves your query, then please mark it as the 'Best Answer' so that the others members in the community having similar problem statement can track the answer easily in future&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Devneet Mohanty&lt;BR /&gt;Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,&lt;BR /&gt;Wonderbotz India Pvt. Ltd.&lt;BR /&gt;Blue Prism Community MVP | Blue Prism 7x Certified Professional&lt;BR /&gt;Website: &lt;A href="https://devneet.github.io/" target="test_blank"&gt;https://devneet.github.io/&lt;/A&gt;&lt;BR /&gt;Email: devneetmohanty07@gmail.com&lt;BR /&gt;&lt;BR /&gt;----------------------------------&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Wed, 11 May 2022 07:19:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/University-Forum/Log-in-retry-logic/m-p/85136#M1518</guid>
      <dc:creator>devneetmohanty07</dc:creator>
      <dc:date>2022-05-11T07:19:00Z</dc:date>
    </item>
  </channel>
</rss>

