1b.app
Link copied -

Fiscalization is successful, but it goes to the stage specified in the fiscalization error

The problem has become more and more frequent. Fiscalization is completed, the receipt ID is recorded, there is data in the logs, but it redirects to the stage specified in the setting "Switch to status in case of receipt creation error".

Can you fix it?

Example of the process https://one-box.shine-bright.com.ua/525140/
Original question is available on version: ru

Answers:

Good morning.
The "Checkbox API: Enable logging of receiving information about checks" setting has been added to integration connections - you can enable it and check on new checks what information the API will issue when requesting information on a check after fiscalization.
I think that maybe in 10 seconds Checkbox doesn't fiscalize the check, that's why we get an error.
08.11.2024, 08:57
Original comment available on version: ua


Tindik Maxim Vadimovich
OneBox production wrote:
Good morning.
In the integration connections, the settings "Checkbox API: Enable logging of receipt information" have been added - you can enable it and check on new receipts what information the API will issue on requests for receipt information after fiscalization.
I think that maybe Checkbox doesn't fiscalize the check within 10 seconds, that's why we get the error.

I just attached a screenshot of the logs, the check is created and the ID is written in the additional field, but the action is transferred to the stage that is indicated in case of an error
11.11.2024, 17:27
Original comment available on version: ru

Did you do exactly what I indicated in the previous comment?
12.11.2024, 09:57
Original comment available on version: ru


Tindik Maxim Vadimovich
OneBox production wrote:
Did you do exactly what I indicated in the previous comment?

oh, sorry, I didn't read it carefully, I'll try
12.11.2024, 11:31
Original comment available on version: ru

example of the process https://one-box.shine-bright.com.ua/526910/
[2024-11-14 20:33:49]
point: /var/www/oneboxshinebrig/web1/web/cron/cron-minute.php
engine_sessionid: 1731609185_662
data: Array
(
[receipt_id] => 48804f8d-****-****-260d-90a14bfa5f7a
[httpcode] => 0
[response] =>
)
15.11.2024, 03:37
Original comment available on version: ru

Example of the process https://one-box.shine-bright.com.ua/546156/ - fiscalization is successful, but did not transfer to any stage. In the logs, everything seems to be in order. I changed the stage manually.
04.12.2024, 17:46
Original comment available on version: ru

again did not move to any stage

https://one-box.shine-bright.com.ua/547937/

fiscalization successful
09.12.2024, 18:28
Original comment available on version: ru

New example: https://one-box.shine-bright.com.ua/563009/ fiscalization successful, but first gave an error
[2025-01-22 21:14:35]
point: /var/www/oneboxshinebrig/web1/web/cron/cron-minute.php
engine_sessionid: 1737573245_5794
data: Array
(
[receipt_id] => a2316d87-****-****-****-f2f1c7f42d97
[httpcode] => 200
[response] => (response deleted)
[2025-01-22 21:14:34]
point: /var/www/oneboxshinebrig/web1/web/cron/cron-minute.php
engine_sessionid: 1737573245_5794
data: Array
(
[receipt_id] => a2316d87-****-****-****-f2f1c7f42d97
[httpcode] => 520
[response] => error code: 520
)
23.01.2025, 17:57
Original comment available on version: ru


Rodion wrote:
New example: https://one-box.shine-bright.com.ua/563009/ fiscalization successful, but first gave an error

Look what happens:
1. you are trying to switch to the stage https://one-box.shine-bright.com.ua/admin/shop/workflowstatus/1229/action/new/ and fiscalize in [2025-01-22 21:14:25] - the request goes through with code 201, fiscalization is expected in up to 10 seconds (the receipt is checked that it is fiscalized)
2. after switching to the "Successful fiscalization" stage after repeated requests to check the end of the receipt fiscalization - you make a request to receive information about the receipt https://one-box.shine-bright.com.ua/admin/shop/workflowstatus/1611/action/new/ - and you are given a 520 error by Checkbox - I understand that we are talking about some restrictions by CloudFlare
And actually because of the error in switching from the stage https://one-box.shine-bright.com.ua/admin/shop/workflowstatus/1229/action/new/ to the stage https://one-box.shine-bright.com.ua/admin/shop/workflowstatus/1611/action/new/ - you get an error - and switches to "Fiscalization error"
I see 2 solutions at the moment:
1. Contact Checkbox support and find out why you get error 520 in some cases - maybe they have certain limits on the number of requests per second or something else
2. In the action "Getting information about the check" enable the settings "Display the error text and continue the transition to the stage" - so that you do not roll back the switching due to an error and do not go into an error
27.01.2025, 17:34
Original comment available on version: ru

got it, thanks, but why does it redirect you to the Fiscalization Error stage? It is written in the fiscalization action, and the error is in the Receipt information action
in theory the process should remain at the previous stage, since it was not possible to move to the stage Successful fiscalization
27.01.2025, 17:53
Original comment available on version: ru

https://1b.app/ru/forum/business-processes/17631-sohranenie-filtra-pokazivat-otk...
I wrote a request for revision in the old topic, does it show up for you or should I create a new ticket?
27.01.2025, 17:58
Original comment available on version: ru


Rodion wrote:
got it, thanks, but why does it redirect you to the Fiscalization Error stage? It is written in the fiscalization action, and the error is in the Receiving information about the receipt action
in theory the process should remain at the previous stage, since it was not possible to move to the stage Successful fiscalization

I described the essence of the problem to you - this is an interconnected switching, a common transaction and its rollback due to an error, because it was not able to switch to receiving information
28.01.2025, 09:05
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment