I'm trying to update from Target extension 1 to Target extension 2 in Launch but I keep getting these errors when I deploy the build to my dev or staging environments:
AT: request failed Error: Errors: sessionId query parameter is required;
AT: [page-init] View delivery error Error: Errors: sessionId query parameter is required;
Looking at the debugger, I see the calls to delivery do not have a value in sessionId:
{"client":"xxxx","sessionId":"","version":"2.1.1"}
If I check the first-party cookies for my domain, I see that I do have a 'mbox' cookie and it does have a value for 'session' in it. I was under the impression that at.js took care of all of this automatically (setting the cookie and pulling its value before sending requests). Am I missing something?
I also get error:
AT: request failed Error: Errors: field - [execute.mboxes] - global mbox is not allowed in mboxes.;
Which I assume is some other difference between Target 1 and Target 2 I have overlooked which may be a separate issue. I also get this entirely unhelpful error message:
AT Error unknown
Solved! Go to Solution.
@reid_from_lulus / @Michael_au: Have you tried updating the Target V2 extension recently?
There have been a few Target V2 extension updates (some just recently) to correct bugs related to sessionID persistence issues and incorrect values generated.
For additional details, check out the Target V2 Launch Extension release notes: https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/adobe/target-v2/release-...
@reid_from_lulus / @Michael_au: Have you tried updating the Target V2 extension recently?
There have been a few Target V2 extension updates (some just recently) to correct bugs related to sessionID persistence issues and incorrect values generated.
For additional details, check out the Target V2 Launch Extension release notes: https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/adobe/target-v2/release-...
Updated to the latest extension and still seeing this issue.
Console error screenshot: https://imgur.com/a/hmhfZEW
Did you find a solution to this in the end? Thanks
Why was this marked as the correct solution when the original poster's problem remains?
I have the same problem, could you solve it?
Views
Replies
Total Likes
I tried by updating latest version but still seeing that error
Views
Replies
Total Likes
Anyone managed to resolve this one yet?
Views
Replies
Total Likes
In my case I just needed to delete whole website storage... couldn't reproduce the error after that.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies