Versions Compared

Old Version 41

changes.mady.by.user Laurent KLOETZER

Saved on

compared with

New Version 42

changes.mady.by.user Antonio PEREZ DIAZ

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Due to the complexity of the interface and the integration and the absence of idempotency, the following error messages are likely to show up.

MessageCauseAction
[External error] Ticket with id 101729574868 [Barcode: 676852034024835003760168] could not be synchronized. The expected ACN is 7063357 but the one received is 7063358. Please open a Support ticket.

Consequences of a legacy bug in barcode generation. Some wrong ACN are still in the database, but we cannot identify them in advance.




Will be definitely solved with that JIRA

Jira Legacy
serverSecuTix JIRA Tracking System
serverIddb7e2039-f715-3f84-b1ed-ba058a819c06
keySTX-130152

In between, execute the following script:

Ticket with id ticketId [Barcode: xxxxxx] could not be synchronized. The expected ACN is expectedACN  but the one received is 7063358. (----).

Code Block
languagesql
update ticket
set additionnal_info='ACN=expectedACN'
where ticket_id=ticketId;


TicketID 101835793445 could not be synchronized due to error: H For ProductCode T23C02-1 GameNumber is 179 but GameNumber extracted from the barcode is 180The ID mapping of the performance did change between the time when the barcode was generated and the time when the synchronization occurred
  1. Add the id to the list of skipped ids
  2. Have the operators reprint the ticket
  3. Communicate to the operators the importance of having the ID mappings rightly set up

[External error] Ticket with id 101812059516 [Barcode: 251146686039192242229055,Container Identifier: 244242,MemberID: 30034444] could not be synchronized due to the provided Membership ID was not found in the Fortress System. Please open a support ticket to investigate this issue.

Data issue, member id is missing in additionnal_info table.


  1. Fix this by script (not needed after this jira)
[External error] Ticket with id 101853377597 [Barcode: 070056601236163218016034,Container Identifier: 245819] could not be synchronized due to multiple card with the same Member Id. Ask Fortress support to fix this on their side.Error on Fortress side. Cause unknown.
  1. Contact Fortress as indicated. In-between, add the ticket ids to the ignored tickets list.
Warning: product T23C02-1 could not be synchronized due to error: H Membership is not Active (FGB_Web)This error message is due to the fact that the tickets has already been synced when V1 of the interface was active.
  1. Do nothing

[External error] Ticket with id 10228770369548 [Barcode: 245051249011197162072689] could not be synchronized: Turnstiles supplied in WS call WD - 18, service supplied inside the barcode 15

This issue occurs when the SFA team sell a ticket and then following the sale, change the entrance associated to the seat on the physical plan. They do this because they sell tickets via a third party for hospitality and allocate the tickets to the third party by selling them initially. Any tickets not sold by the third party are then changed to a premium ticket and the entrance of the seat is changed to be sold to the general public at a slightly higher price. 

  1. Skip tickets impacted already cancelled/invalidated
  2. Reprint valid tickets



Frequent Asked Questions (FAQ)

...