Session Timeout occurring - REST API

REST
1

I haven’t seen this error of session timeout until recently. The error I am getting is:

{“message”:“Session timeout”,“code”:3091}

This happens when I am adding rows to my tables. My current settings which I don’t think should be contributing to the timeout values are:

Enable Session Timeout: Inactivity timeout: 300 sec

What has had in my application is that I’ve logged in successfully one time and I’ve added many rows to my tables and also uploaded files.

I don’t know why this is happening and wondered if there are any other considerations of timeout values that I needed to worry about?

2

Do you send the “user-token” header on all requests after you login?

3

Yes I do send the user-token that I receive after login API call is issued.

4

Did you notice if it takes about 5 minutes after the login when you get the timeout error?

5

I don’t know if it was ~5min. but there was a minute or two before I saw this error.

6

Thanks, we will try reproducing it.

7

Hi Roy,

We were unable to reproduce this problem, the feature works as expected - the timeout is extended by the specified time after every invocation. If you could come up with a sample code demonstrating the problem, it would be very helpful.

Regards,
Mark

8

Have to thrown in some info that I mistakenly omitted. The Enable Session was set to 300 secs but was not enabled when reporting this problem.

9

That explains it. If you enable it, then the behavior would be as expected.

10

By not having a session timeout enabled, then wouldn’t the logged in session be infinite in usage?

11

It is not infinite, should be 1 hour. We’re checking this use-case as well.

12

Okay so there is 1 hour default session timeout. This time limit is for in activity only?

13

Yes. it is the same as setting the session duration to 1 hour.

14

This is good to know since I’ll have to code for this activity.

I will keep an eye on this session timeout, since I’m fairly certain that a user can login and and perform add/deletes , etc. and it doesn’t expire for this 1 hour threshold.

15

My user logged in at 10:30:40:758 and the last activity was at 11:59:23:732. I had the Enable Session Timeout set to 600 seconds. I then disabled this Session Time out and I immediately get the error:

{“message”:“Not existing user token. Relogin user to update your user token”,“code”:3064}

Can you explain?

16

When you disable the “Enable Session Timeout” all sessions are invalidated and users must re-login.

17

Thanks much for the info.

18

I currently do not have Enable Session Timeout enabled. My user has been currently logged in and adding/deleting data for more than two hours now. I thought the default of 1 hour sessions timeouts would be applied here but so far they are not. Can you shed more light on this subject?

19

Just like when the sessions are enabled, it is 1 hour after the most recent invocation. Every request within 1 hour extends the life of the session by another hour

20

Thanks , that does help my understanding now