Action "Update order status in Rozetka Seller API" gives strange message / rozetka_order_status_action_change_status
I start the action through the procedure in this order https://baza.cn.ua/admin/customorder/order/31157/edit/
Here is the procedure https://baza.cn.ua/admin/shop/workflow/12/procedure/43/?status=0
I get an incomprehensible error "There was a pardon."
Also in the logs https://baza.cn.ua/admin/logs/showall/ajax/?file=rozetka-2020-12-21.log
Nothing shows that there was an attempt to appeal
I think that this is not normal, because when contacting the TP sockets, they immediately ask what and how you send and where it should all be in the logs (logically) well, to simplify the life of developers, so that you don’t write to you constantly for each request that you send it provided, and the user could take this information himself in the logs and in the message
I beg:
1. Make the error informative (at least a stupid answer from the api outlet or server)
2. Write attempts to send requests to the logs
Original question is available on version: ru
Here is the procedure https://baza.cn.ua/admin/shop/workflow/12/procedure/43/?status=0
I get an incomprehensible error "There was a pardon."
Also in the logs https://baza.cn.ua/admin/logs/showall/ajax/?file=rozetka-2020-12-21.log
Nothing shows that there was an attempt to appeal
I think that this is not normal, because when contacting the TP sockets, they immediately ask what and how you send and where it should all be in the logs (logically) well, to simplify the life of developers, so that you don’t write to you constantly for each request that you send it provided, and the user could take this information himself in the logs and in the message
I beg:
1. Make the error informative (at least a stupid answer from the api outlet or server)
2. Write attempts to send requests to the logs
Answers:
Kupriyan Vladislav Valerievich wrote:
I think it's not normal
This is your subjective opinion based on a specific need.
In practice, most users do not understand what is in the logs and, at the first misunderstanding, they write to the forum or call their manager.
Kupriyan Vladislav Valerievich wrote:
1. Make the error informative (at least a stupid answer from the api outlet or server)
There and so now it gives an error "Update locked by purchase status"
Kupriyan Vladislav Valerievich wrote:
2. Write attempts to send requests to the logs
Logging is an individual thing. Some people need it, some don't.
If you need logging of all requests (or some specific ones) - describe what you need in what form - we will evaluate the revision depending on the amount of work.
22.12.2020, 16:07
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
Copyright © OneBox 2024
