This is an environment issue and we need to make sure that these settings account for using services like Bulk-edit or Lists where it may take some time for jobs to complete.

actually I can’t see RT in headers as well, mb one more browser quirk

even if the RT TTL is an hour

I don’t say 1 hour is enough, it’s just a confirmation that it’s equal to AT expiration and no refresh requests are sent. RT TTL should be much more longer than AT TTL

I can’t know if people experienced issues with other modules - now it sounds like session is 1 hour in total, and it could be noticed by QAs who track long running jobs

, even if the RT TTL is an hour, that’s not long enough in the scope of a job that “may last a few hours” if there is no interaction with other APIs during that time. As to “I don’t see RT cookie”: I think this is just a browser quirk. I perpetually have problems getting browsers to correctly show cookies: there will be nothing in Application > Cookies, yet I can plainly see them in the request headers of the network inspector and in the response from the login request. It’s super frustrating, but I don’t think it’s the source of the problem here.

actually on bugfest RT TTL is 1 hour (similar to AT), but I don’t see RT cookie - mb it’s a cause of it

probably you would be interested to take a look as well

Hey and - we think it the RTR refresh token is set too short (10 minutes). You guys should ask Kitfox to update the RTR refresh token to a timeframe that aligns with bulk-edit needs and then re-test.

We should discuss adding this information to release notes.