When an AWS SSO session expires, Dynobase does not do a good job detecting this and hangs until timeout when running a query. Once the app is responsive again, the user has to select "Reload Profiles" from the Dynobase menu to re-authenticate, which works, except it then wipes out your existing query or work. You have to start whatever you were doing over.
Because of AWS session limits, I have to do this 2-3 times a day, which makes usage frustrating. It would be great if:
1) Expired SSO Sessions were detected and proactively reloaded if the app has focus.
2) My existing query did not disappear during the session refresh.
Version 2.0.1
When an AWS SSO session expires, Dynobase does not do a good job detecting this and hangs until timeout when running a query. Once the app is responsive again, the user has to select "Reload Profiles" from the Dynobase menu to re-authenticate, which works, except it then wipes out your existing query or work. You have to start whatever you were doing over.
Because of AWS session limits, I have to do this 2-3 times a day, which makes usage frustrating. It would be great if: 1) Expired SSO Sessions were detected and proactively reloaded if the app has focus. 2) My existing query did not disappear during the session refresh.