Server call getting cancelled

[AEPAA]

We have click rule which has a event click with a css selector as anchor tag. Rule is pretty small without any conditions. Custom code in the set Variable action is pretty small. I'm just fetching some of the data attribute in action and mapping it to eVars. We see beacons are getting cancelled for the rule , does anyone have any idea ?

Even though server call getting cancelled with 307 as status. We see partially data being captured in Adobe Analytics. Has anyone faced such issue ? 

Note : Unfortunately I can't use time delay. 

[Elanchezhiyan_E]

Hi @AEPAA,

This issue might occur due to sudden page navigation, I have also encountered this issue.

With a slow internet connection, the data might be posted. sometimes it gets rejected, resulting in a partial data being received.

When you click on the anchor tag, if the page is redirected, it would be better to store those information in sessionStorage or localStorage and send the information and corresponding event in the next page view call. This way, you will be able to see more data.

Good Luck..!

[harishkumar]

@AEPAA mostly due to navigation, data does not get processed however since you are mentioning its partially processed, there could be some other reason too. 

Best would be to extract data feed for that specific hour and understand what is capture in pre-column. 

I hope this help you drill down to understand more details on data processing at adobe.

[Jennifer_Dungan · Accepted solution]

Unfortunately, this is a timing issue and these are really hard to deal with some times... it's also possible that the calls are making it to Adobe, but the image pixel response isn't making it back to you... this can look like a false failure, when in fact the tracking was actually successful, but its impossible to know for sure what did and didn't make it... 

Sometimes I will cheat... and instead of trying to track the click, I use the click rule to set a value into session storage, then on the next page, read the session storage (if it exists), append the tracking to my page view, then delete the session storage item to ensure I don't double track it....