Open icougil opened 4 years ago
I found how to solve (at least manually the issue) !
Going to the "Reservations" part I found tooo many in "In process".
What I did basically is selecting the oldest one (the one that probably had the problem) and I cancelled the reservation.
Doing this, the process now continues and at least is able to cancel the rest of the "In process" Reservations ;-)
Hi @cougil, thanks for the report.
I suspect that cancelling the pending reservation didn't solve the issue of why that reservation couldn't be deleted in the first place.
I imagine you've direct access to the database. If so, can you please run the following query?
select count(*) from ticket where tickets_reservation_id = '<reservation-id-here>'
this should return 0. Unless the tickets are still attached to the reservation, which would be wrong.
other questions:
Thank you very much for your help!
Hi @cbellone
Yes, finally cancelling the Reservation solved the issue and then now no Reservations are in progress.
I ran the query and the result is 1 record 😓
Regarding your other questions: no, alf.io didn't generate an invoice for that reservation.
About the audit log, here you have it (I've obfuscated personal/sensible data):
Type Date User Entity type Entity id Modifications
RESERVATION_CREATE 04.03.2019 09:43 - RESERVATION 282e47a0-7746-402e-bb83-54f89c38614d
UPDATE_TICKET 04.03.2019 09:44 - TICKET 857
[
{
"newValue": true,
"propertyName": "/assigned",
"state": "ADDED",
"oldValue": false
},
{
"newValue": "xxx@xxx.com",
"propertyName": "/email",
"state": "CHANGED",
"oldValue": ""
},
{
"newValue": "xxx",
"propertyName": "/firstName",
"state": "ADDED",
"oldValue": null
},
{
"newValue": "xxx xxx",
"propertyName": "/fullName",
"state": "CHANGED",
"oldValue": ""
},
{
"newValue": "xxx",
"propertyName": "/lastName",
"state": "ADDED",
"oldValue": null
},
{
"newValue": "LARGE",
"propertyName": "/{tShirtSize}",
"state": "ADDED",
"oldValue": null
},
{
"newValue": "M",
"propertyName": "/{gender}",
"state": "ADDED",
"oldValue": null
},
(...)
{
"newValue": "xxx xxx",
"propertyName": "/{Last question}",
"state": "ADDED",
"oldValue": null
}
]
UPDATE_TICKET 04.03.2019 09:45 - TICKET 857
[
{
"newValue": "ACQUIRED",
"propertyName": "/status",
"state": "CHANGED",
"oldValue": "PENDING"
}
]
TERMS_CONDITION_ACCEPTED 04.03.2019 09:45 - RESERVATION 282e47a0-7746-402e-bb83-54f89c38614d
[
{
"termsAndConditionsUrl": "https://xxx.com/conditions.html"
}
]
RESERVATION_COMPLETE 04.03.2019 09:45 - RESERVATION 282e47a0-7746-402e-bb83-54f89c38614d
UPDATE_TICKET_CATEGORY 19.03.2019 17:33 - TICKET 857
UPDATE_TICKET_CATEGORY 20.03.2019 00:06 - TICKET 857
UPDATE_TICKET_CATEGORY 23.03.2019 18:18 - TICKET 857
UPDATE_TICKET_CATEGORY 24.03.2019 23:49 - TICKET 857
UPDATE_TICKET_CATEGORY 15.05.2019 12:16 - TICKET 857
UPDATE_TICKET 12.12.2019 00:27 - TICKET 857
[]
RESERVATION_COMPLETE 12.12.2019 00:27 - RESERVATION 282e47a0-7746-402e-bb83-54f89c38614d
Hope it could help.
Best regards,
Thanks @cougil ,
From what I can see, the reservation was created on 04.03.2019 09:43
and then confirmed on 04.03.2019 09:45
. That was 9 months ago. Weird.
Additionally, the reservation has been completed once again on 12.12.2019 00:27
, and the timing is consistent with your second comment. So I guess it was you.
Anyway this would explain why the ticket is still linked to the reservation. Because the reservation was not cancelled.
I need to understand more. Can you please post the output of the following queries to check if everything is fine on the DB:
-- this query contains the total number of seats for each event defined
select id, available_seats from event;
-- this query checks if the number of seats available is consistent with the one declared. This must be true for all events
select id, available_seats = (not_allocated_tickets + pending_tickets + sold_tickets + released_tickets + checked_in_tickets + dynamic_allocation + not_sold_tickets) as seats_match from events_statistics order by 1;
-- this shows the categories defined for each event.
select event_id, ticket_category_id from ticket_category_statistics order by 1, 2;
-- this checks what is the ticket category for the ticket linked to this reservation
select event_id, category_id from ticket where id = 857;
thanks
Describe the bug It seems that the
cleanupExpiredPendingReservation
is failing trying to cleaning up some not finished reservations.To Reproduce Don't know how to reproduce it, sorry 😅
Expected behavior What we should expect is probably let the job continue and not fail, because starting from then, all the "pending" Reservations are not going to be cancelled and they will remain forever in the system.
Screenshots
Stacktrace
Version: v.2.0-M2-SNAPSHOT
Desktop (please complete the following information): N/A
Smartphone (please complete the following information): N/A
Additional context Add any other context about the problem here.