JavaScript error with at.js 2.1.1

gokula

06-11-2019

Hello Team,

we’re logging the following JavaScript errors on our site.

  • Visitor API requests timed out (approx. 130 errors per day)
  • Disabled due to opt-out” (approx. 400 errors per day)

These both appear to be coming from the Adobe Target at.js library 2.1.1.  @

How can we resolved that? Is there any configuration needed.

Thanks,

jantzen.belliston-Adobe


Amelia Waliany

Accepted Solutions (1)

Accepted Solutions (1)

Shruthi_N

Employee

07-11-2019

gokula​ Without seeing the actual errors and the logs, its hard to determine what might be causing them. If you can log a customer care ticket with the logs along with any steps to reproduce these errors we can take a look. To submit an incident please send an email to customercare@adobe.com .

Thanks.

Answers (10)

Answers (10)

gokula

11-11-2019

Hi Surebee -

No increasing the timeout still showing the error in Prod which is really matter of concern for us.   Same thing for Disabled opt out error.

I'll raise the client care ticket with P1.

Thank you. 

Shruthi_N

Employee

06-11-2019

@gokula , Could you please provide more details on the error? WHat is the exact error that you are seeing? Any screen shots and url where we can reproduce the error would be helpful . Also are there any steps to reproduce the error?

Amelia_Waliany

Employee

22-04-2020

Hi @gokula

 
Our next Adobe Target Skill Builder Webinar is right around the corner on May 5th, and will be presented by Adobe Target Product Management on migrating Adobe Target’s mbox.js to At.js. Check out this community discussion to register today. Hope you can make it!
 
Warmly,
Amelia 

surebee

Employee

10-11-2019

Thanks gokula. Did increasing the timeout make a difference in the frequency of the timeout errors?

Do you have any screenshots/logs/URL you could provide where the issue is reproducible (the disabled due to opt out error)?

gokula

08-11-2019

Hi Surebee,

Yes, Visitor API timeout default only.    visitorApiTimeout: 2e3,

but after your above reply, I just thought to add in custom way like below

window.targetGlobalSettings = {

    visitorApiTimeout: 3000 // using custom API timeout 

};

About Disabled due to opt out - It's just showing in the at.js 2.1.1

Not sure from where is getting triggered.

surebee

Employee

08-11-2019

The visitorApiTimeout setting in at.js is set to 2s by default. If you have not changed this setting, it should still be 2s. Could you please confirm?

If you have not implemented the Opt out link for Target, then I am not sure why you are seeing the "disabled due to optout error". To confirm, is this error being returned in an mbox call?

Like Shruthi mentioned, we would need to look at a URL and or logs to either replicate the error or to understand what is causing them.

gokula

08-11-2019

Hi Surebee,

Is both configuration mandatory? 

we haven't set any custom configurations. We've just followed the document Upgrading from at.js 1.x to at.js 2.x  and implemented and upgraded the library month's ago.

I have not seen Adobe specifically mentioned about above configurations and  we had issues with up-gradation too that time we raised the client care ticket and solved the issue but even client care not communicate about these configurations

Do I need to implement these things as custom way?

Thanks,

surebee

Employee

08-11-2019

Hi @gokula,

For the "Visitor API requests timed out" error: what is the visitorApiTimeout in your Target library?

For the "Disabled due to opt-out" error: have you implemented the opt out link on your site/pages?

gokula

07-11-2019

Hi Shruthi

Thanks for the reply. I'm afraid, you can't see the errors in console, as these errors getting logged in our AppDynamics tools.

I can share the log's with you which comes with URL. Do you want me to share the log's here?

I mainly find it strange that these are occurring as errors on the page – it feels like something that should fail a bit more silently.

My concern is .. Is it something we missed in our configuration / implementation or Is Adobe already aware of these error's and waiting for us to report it