It looks like a checkbox jamb. The history of requests from us to the checkbox is as follows:
2022-10-03 09:16:03
https://api.checkbox.in.ua/api/v1/receipts/sell{"id":"71c1de75cb3040dbb9dc72220c209421","goods":[{"good":{"code":"342541","name":"\u0420\u044e\u043a\u0437\u0430\u043a \u0437 \u043f\ u0440\u0438\u043d\u0442\u043e\u043c","barcode":"","price":58000},"quantity":1000,"is_return":false}],"payments":[{"type" :"CASH","value":58000,"label":"\u041f\u0456\u0441\u043b\u044f\u043f\u043b\u0430\u0442\u0430"}]}
answer:
{"message":"Change not opened"}
the same at 2022-10-03 09:23:32
then at 2022-10-03 09:24:44
{"id":"71c1de75cb3040dbb9dc72220c209421","goods":[{"good":{"code":"342541","name":"\u0420\u044e\u043a\u0437\u0430\u043a \u0437 \u043f\ u0440\u0438\u043d\u0442\u043e\u043c","barcode":"","pric
e":58000},"quantity":1000,"is_return":false}],"payments":[{"type":"CASH","value":58000,"label":"\u041f\u0456\ u0441\u043b\u044f\u043f\u043b\u0430\u0442\u0430"}]}
answer:
{"message":"The specified check id already exists"}
That. on the first 2 requests, we received the answer that the shift is not open (here, most likely, you did not start the action of opening the shift). And then, after the shift was probably opened, we get the answer "The indicated check id already exists." But we did not successfully transfer such a check to the checkbox.
You need to write in support of the checkbox and specify why we receive the answer "The indicated check id already exists" when such a check has not yet been created.
I suspect that if the change has not been opened, the check somehow keeps it and does not allow the same one to be made.
I also think that if you open the shift immediately in the morning before creating all the checks, then everything will be okay.