at.js unreachable "serverDomain", but default content doesn't show. any failsafe solution? | Community
Skip to main content
T
tongc54876562
Level 2
July 20, 2016
Solved

at.js unreachable "serverDomain", but default content doesn't show. any failsafe solution?

  • July 20, 2016
  • 5 replies
  • 1904 views

in at.js I can see serverDomain is configured. In the case of serverDomain is not reachable (server down or whatever), our webpage stays as blank. I think this is due to the fact that body{opacity:0} is never removed in the case of failing to access the serverDomain.

Is this a bug or there is a configuration that can give me failsafe?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ParitMittal

Hi 

We checked from our end that you are using at.js V0.8.0 and it had same issue and were rectified in V0.9.1 Hence we would recommend to use at.js V0.9.1 . 

Also, There is a variable timeout:5000 which controls for how long will we wait to call. Time out 5000 means we will show the page in 5 secs in case of unreachable edge.

Thanks & Regards

Parit Mittal

5 replies

ParitMittal
ParitMittal
Level 10
July 22, 2016

Hi ,

Ya, it should never remain blank. Can you provide more details?  .Please share your Client code and Target Account login details as well as the Test URL in a private message so that we can simulate the issue at our end.

Thanks & Regards

Parit Mittal

T
tongc54876562Author
Level 2
July 22, 2016

try http://tongc.github.io/ and you can see the page is blank because Adobe Target URL is not reachable. 

ParitMittal
ParitMittalAccepted solution
Level 10
July 25, 2016

Hi 

We checked from our end that you are using at.js V0.8.0 and it had same issue and were rectified in V0.9.1 Hence we would recommend to use at.js V0.9.1 . 

Also, There is a variable timeout:5000 which controls for how long will we wait to call. Time out 5000 means we will show the page in 5 secs in case of unreachable edge.

Thanks & Regards

Parit Mittal

T
tongc54876562Author
Level 2
July 25, 2016

Thanks Parit, my file was less than a month old but seems already very stale. (looks like 11 versions in between). Because we can't use latest file without having a release which is rather time consuming so I wonder if there is any release note for at.js so that we can understand what have been changed and decide if it worth upgrading or not.

Terms & ConditionsAccessibility statement

Loading footer...