Replicon slow to authenticate and states all users are offline after authentication

  • 3
  • Problem
  • Updated 3 years ago
  • Solved
Pretty much what the title says. Replicon takes over 5 minutes to authenticate and render our users' timesheets. After the timesheets are rendered, Replicon locks the timesheet as read-only and states our users are offline.
Photo of Alan Ho

Alan Ho

  • 12 Posts
  • 1 Reply Like
  • extremely frustrated

Posted 3 years ago

  • 3
Photo of Lingaraj Dharwad

Lingaraj Dharwad, Product Champion

  • 1100 Posts
  • 46 Reply Likes
Hi Alan,

Thank you for using Replicon community,

Our server team working on resolving this and we will update this thread as soon as its resolved. 

We apologize for the inconvenience caused and appreciate your patience. 

Thanks,
Lingaraj
Photo of Alan Ho

Alan Ho

  • 12 Posts
  • 1 Reply Like
Is there an estimate as to when this will be resolved? 
Photo of Lingaraj Dharwad

Lingaraj Dharwad, Product Champion

  • 1100 Posts
  • 46 Reply Likes
Hi Alan,

The issue should be resolved now. Can you check with your end users and confirm? 

Thanks,
Lingaraj
Photo of Alan Ho

Alan Ho

  • 12 Posts
  • 1 Reply Like
It looks like our users are back up and running. Thanks for the quick resolution.
Photo of Lingaraj Dharwad

Lingaraj Dharwad, Product Champion

  • 1100 Posts
  • 46 Reply Likes
Hi Alan,

Thanks for the confirmation. We noticed a small spike on one of our endpoints, this was immediately taken care by the server team. So should users still complain. Simply have them log out and log back into Replicon. 

Regards,
Lingaraj
Photo of April

April

  • 18 Posts
  • 2 Reply Likes
I too have been having this issue particularly on Monday's and Fridays. Is Replicon working to fix this overall issue? I understand it is fixed now but the problem persists almost weekly.
Photo of Lingaraj Dharwad

Lingaraj Dharwad, Product Champion

  • 1100 Posts
  • 46 Reply Likes
Hi April,

Yes, work is underway to make scaling fully automated, we can assure you that spikes like today's will be handled in a much better manner in the future. This was one of the reasons for us moving to Amazon Web Services this year. 

Thanks,
Lingaraj