POST /Templates/{templateId}/Order/{orderId}/Confirmation (problem with 15.1)

Tushar Samant $organization over 6 years ago

Here is a problem we are seeing since our recent upgrade from 14 to 15.1.

This is a custom web site, and we send order confirmations from here. The rendering of the confirmation email is done on the Tessitura side.

We are now sporadically getting a 400 response code on the /Templates/{templateId}/Order/{orderId}/Confirmation call. The error message is "Specified LoginName already exists for this WebLogin."

Without going too deep into the web code, I can confirm that:

The constituent doing the checkout (POST Web/Cart/Checkout thinly wrapped) is the same as the one making the render call. They happen in succession.
The constituent is "special" (named anonymous) and handles more orders than typical.
Not all render calls in this situation fail. 80% to 90% succeed. It's not clear how to replicate this.

More mysterious behavior:

The response body has always been correct so far. Only the response code is 400. (Ignoring it will likely be our workaround for now.)
When testing, the same call failed, occasionally. But the error message was about seat locking! Again, it was random, we couldn't replicate it.

BTW the template has no strange code. It's essentially the example template that ships with Tessitura, with extra markup.

Maybe a minor bug in the rendering call?

Tushar Samant

Chicago Architecture Center

Tom Brown (Past Member) $organization over 6 years ago

Do you have any indication about the kinds or computers/clients software that are associated with these errors?

Last week we were chasing done an error that may be related to Android devices. I'm wondering if you have seen something like that in this case?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Tushar Samant $organization over 6 years ago in reply to Tom Brown (Past Member)

Hi, Tom,

The whole web app runs on a single platform: LAMP, aka Mysql and PHP. We don't have a separate mobile app. The API calls are technically hand-coded but essentially just PHP's built-in facilities.

I would still be interested in the details of what you found. I had to put in at least one workaround for a quirk that seems .NET specific. Maybe another is needed.

Thanks!

Tushar
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Tushar Samant $organization over 6 years ago

Got a failure today with "Seat Locking problem" as the error message. Code 400.

All else is identical with previous failures.

Still seems like a bug in the email rendering API.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Kim Lee $organization over 5 years ago in reply to Tushar Samant

Hello, I've come across this post as we have recently found we are occasionally getting the Seat Locking Problem error when executing

TXN/Orders/{orderID}/PrintTicketElements on our custom website. Thought I would reach out in case you discovered more about why this was happening.

Thanks in advance!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Matt Belanger $organization over 5 years ago in reply to Kim Lee

Hi Kim. I would recommend you go ahead and put in a support ticket by emailing hello@tessituranetwork.com so we can go over this with you, if you don't get a response from Tushar. The specifics of your implementation are likely to play a role in our ability to help you resolve this sort of error.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Kim Lee $organization over 5 years ago in reply to Matt Belanger

Thanks Matt, will do
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel