Hello, I had faced the fallowing error when the user opened the transactions follow-up page in a transactions project: Unexpected token '<', "html><hea" __is not valid JSON
Note that, I gave access to a user outside our Appian servers, and the user faced this error. we didn't use any authentication method for the user login. Did anyone see this error before or knows whats its problem.
Discussion posts and replies are publicly visible
I think we need way more details to understand what might go on.
What does "Note that, I gave access to a user outside our Appian servers, and the user faced this error. we didn't use any authentication method for the user login" mean?
The scenario is as follows: I developed a money transaction system for my organization using appian. Now, we wanted to extend this system to be used by our customers in their offices. so we gave them the site link to access it and open appian from outside the environment. When the customers opened it, they faced the shown error which left us wondering. The project works correctly.
Have you ever saw such a error like this?
I have never seen such an error. And I wonder how your customers would access Appian without login credentials.
Hi,I have experienced the same error with our users.The context is quite the same : it concerns users who access our server (on-premise) from Internet.The users are authenticated and the connection between the user and our server is made through a network device (a netscaler).
I need to experiment more because it is hard to reproduce.
Hi and Happy New Year !We finally found the origin of this error : it is due to a timeout on one of our intermediate network gear between the browser and the APPIAN server.It's a network equipment where an idle timeout is set to 60 minutes while our Appian instance sets an idle timeout to 65 minutes : it makes APPIAN crashes because the network session ends before.The solution is to reduce the APPIAN Idle timeout to make it lower than the network equipement. In that way, APPIAN will correctly handle the session timeout and the application won't crash.
Great, I've been searching for a solution to this for a long time and still can't find it, glad you solved it word wipe
Thanks. I also got the same problem. Now, I solved it. tiny fishing
Could you please confirm where exactly that you have reduced the APPIAN Idle timeout, do we need to check any specific condition for reducing timeout
Hi,
The Idle Session Timeout was changed from the Admin Console interface (https://docs.appian.com/suite/help/24.2/Appian_Administration_Console.html#session-timeout).No specific check is needed before, except in my case where I needed to know the intermediate timeout that was set, in order to be sure the Appian Timeout is below.
Okay got it thank you for the confirmation