Improve server page-timout

What is a one sentence summary of your feature request?

Improve server timeout handling

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

it often happens that you are staying on a EPP page for a few minutes and if you then try to save the changes you made it results in a “Cannot execute command! An error occured!” error.
This is extremely annoying because then all your changes are gone and you have to do it all over again.

I already contacted the support and the main responds was “there is nothing we can do about it”. Ticket#00477680
As I am not aware of any other software with such an aggressive token timeout implementation, I surely think there is something that can be done.

How do you currently solve the challenges you have by not having this feature?

reload the page and make the changes all over again

Upload any supporting images that you think should be considered in this idea.

Hi,

Thank you for the feedback and sorry to hear the support interaction wasn’t more helpful — this actually has a straightforward solution we should have pointed you to sooner.

EPP already allows you to configure the session timeout duration directly from the console. You can find it under System Configuration → System Settings → Session Settings /Timeout (min), where you can set it anywhere between 5 and 60 minutes (default is 15 minutes). There is also a Timeout Counter setting that controls the warning countdown before the session expires.

Adjusting those two values to better fit your workflow should resolve the issue you’re experiencing.

No, that is not correct. This simply adjusts the timeout until you get logged out of the server. This has nothing to do with my feature request

Hi ,

You’re right, and I apologize for the misdirection — the session timeout setting controls logout behaviour and doesn’t address the save error you’re describing.

I understand now that the actual request is for the application to handle this scenario more gracefully, so that changes are not lost when a save operation fails in this way. I’ve noted this as a feature request and it’s something we’ll be looking at going forward. in our future releases

We’ll keep you updated here as there is progress to share.

Hi, ok got it. Correct, the feature request is for EPP to EITHER

  • eliminate those token timeouts completely and only have the session timeout(settings) in place or
  • have another workaround to handle it more “gracefully” as you said.

Looking forward to updates on this matter.