Firstcall Catalog Session Expired Message

[sbebenelli]

Any idea why I get this message with the Firstcall catalog and what's the fix?

[rhillig]

We get that message quite often. We have to go out of the program completely & come back in - then it works.

[timbre4]

Support is asking if you are seeing this time out message in the afternoon?

[rhillig]

I do think we have gotten it more in the afternoon than the morning. I just figured that we have had too many people in the same parts vendor at the same time. I will pay more attention to when we are getting it.

[sbebenelli]

Support is asking if you are seeing this time out message in the afternoon?

It seems to me it's in the afternoon. Not everyday but it does seem like it's more often than it used to be.

[Silky7]

With any SSL connection, the time and date are a factor, so do make sure those are as accurate as possible. I could only speculate, as this timeout is coming from FirstCall, but we used to have a similar problem with our Estimator integration. Back then we'd authenticate only once, then track that session for the whole day. If you were inactive on the site for a certain period, you'd be timed out and receive a similar message.

Typically the best way to avoid a session timeout is closing the site if you're not using it. It would also be a good idea to check with O'Reilly to see what duration their sessions are set for; they may be able to increase them.

[rhillig]

I have had this with both Oreilly & Auto Value