Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Target Extension 2 in Launch not sending sessionId

Avatar

Avatar
Boost 3
Level 1
reid_from_lulus
Level 1

Likes

3 likes

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile

Avatar
Boost 3
Level 1
reid_from_lulus
Level 1

Likes

3 likes

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile
reid_from_lulus
Level 1

08-09-2019

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

Accepted Solutions (0)

Answers (0)