I would like to know as to what exactly happens behind the scene when an AA server call request shows its response status as canceled(in red) instead of 200OK in the chrome browser network? As the analytics call has hit the Adobe data collection server - does it processes the data further or rejects it? If it rejects the data, on what basis it does that?
not sure if it is really "not tracked"... problems with proxy/IP or similar would lead to another status code instead of "cancelled" ...
another problem might be that the browser navigated immediately after the server call. I mean it sent the data, navigated to next page (eg. on a exit link) and cancelled the request to not wait the "response". if that's the case, the data has been sent but browser did not wait for the server response...
I tested this myself today, by adding a querystring parameter to the URL so I could segment my visit once it was baked into AA
There are some clicks I encounter which navigate away from our page which I believe is what causes the cancellation, same as captured in your Abhinav's screen shot
While generating my data I tallied the Success Events I expected to see after the session was processed. Some of the calls were cancelled and some of those same clicks made it out before the page unloaded
In my case the same number of clicks I executed, both Cancelled and 200 were counted in AA Workspace
I suppose the fix to fully prevent the cancellation in the case of a quick unloading of the page, is to increase the delay in s.tl() or activate the 100ms delay within the Launch rule handling that event