05-24-2017 09:59 AM
Hi @JeanRV,
It is a normal practice to mark an issue as resolved when there is no further input from the user.
As user might not be online frequently, so it is also OK to reopen an issue, by marking ad not resolved.
It the error only happen after two hours, then I guess it is working as expected. As there are session timeouts for active connections. When there is no communication after the timeout lapsed, the post action will fail ad the token is expired.
05-24-2017 10:58 AM - edited 05-24-2017 11:03 AM
Thanks @YK1001! You are correct — a login session will not continue indefinitely; if you start a post and take several hours to complete it, you will likely be logged out (hence the authentication error) in the interim. Hope this is helpful @JeanRV.
A friendly reminder when escalating issues and interacting with other Local Guides — please be kind, patient, and understanding. Help us make Local Guides Connect a friendly and helpful place to be. Respect the moderators and each other. Local Guides is a global community comprised of many different languages, time zones, ages, and levels of expertise. Everyone is welcome.
Refer to this post for more guidelines about Connect etiquette.
05-24-2017 05:52 PM
Thanks @YK1001 and @MegS for your replies.
@YK1001, you wrote: "It the error only happen after two hours, then I guess it is working as expected. As there are session timeouts for active connections. When there is no communication after the timeout lapsed, the post action will fail ad the token is expired". I would like to tell two things:
@MegS, I did read the post for more guidelines about Connect etiquette several times before posting messages and I tried to follow the guidelines. I did not want to be rude, unfriendly or disrespectul with moderators. I was trying to help improve the system. By the way, English is not my first language and I am sorry if my way of writing in English makes you feel I am unfriendly or disrespectul. I would appreciate any advice to improve my English writing.
05-24-2017 08:34 PM
Hi @JeanRV,
There were too much jumping in my replies, I am sorry for that and let me try again.
1. First of all, the exact error message is not helpful (even meaningless) to end users like us.
2. By experience,. I know that type of message is due to session timeout.
3. But session timeout can have different reasons. The issue behind is a lost or expiration of session token or cookie.
4. I have see some random lost of session token before. So if every posting action result with an error, then it is problematic
5. If lost of token is by normal timeout, then it is working by design
6. We do not know what is the exact login session timeout. It used to be half hour, two hours. I guess it is two hours at the moment.
7. The session timer, I guess, is not activities bases. So it can timeout even we are typing a post.
Thus when our main login session cross two hours since we start compose a post but before clicking post, the timeout happen, and session token is expired.
This results with all kinds of debug code.
Hope this can help!