SAML SSO killing running notebooks

We have a customer who is running JupyterHub in AWS w/SAML SSO enabled. SSO is timing out the web sessions and disconnecting our users from long-running notebook jobs. Looking for a workaround so that when users reconnect their notebook sessions are either persistent or recoverable. Any suggestions would be greatly appreciated.

When you disconnect the notebook should continue running in the background. The outputs in the notebook won’t be updated:

but if the notebook saves any persistent outputs e.g. files they should be available.

Are you able to modify the SSO timeouts?