Getting Target timeout error

Avatar

Avatar
Validate 1
Level 2
bharath_sampath
Level 2

Likes

7 likes

Total Posts

8 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
bharath_sampath
Level 2

Likes

7 likes

Total Posts

8 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile
bharath_sampath
Level 2

02-12-2016

Hello,

We are having issues where our webpages are loading, but our target-global-mbox is hiding the content.

In the console, there is an error that says "[Target] executeAjax(): timeout : timeout".

When we refresh the page, it seems to go away sometimes, but seems to recur a lot on IE.

This issue occurs randomly and we are not able to point out the cause of this.

We migrated to at.js recently in our staging environment, but I do not think this is the cause of the issue.

I've attached a screencapture.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
bharath_sampath
Level 2

Likes

7 likes

Total Posts

8 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
bharath_sampath
Level 2

Likes

7 likes

Total Posts

8 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Affirm 1
View profile
bharath_sampath
Level 2

20-12-2016

We scheduled a meeting with our Adobe support team and they had a developer take a look at it. It turned out to be a bug in at.js which failed to "unhide" the mbox by removing the "mboxDefault" class from our mbox wrapper div when the call to Target timed out. Just wanted to update the status and share this general bug with others.

Answers (1)

Answers (1)

Avatar

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,338 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile

Avatar
Validate 1000
Community Manager
jantzen_belliston-Adobe
Community Manager

Likes

339 likes

Total Posts

2,338 posts

Correct reply

819 solutions
Top badges earned
Validate 1000
Springboard
Validate 500
Validate 250
Validate 100
View profile
jantzen_belliston-Adobe
Community Manager

06-12-2016

Hi,

It sounds like this may need to be looked at in further detail. It may even be a bug. I'd suggest opening a ticket with Target support via ttclientcare@adobe.com.

Thanks,
Jantzen