Ukrposhta status not being processed
Возникают сложности в работе почтовых сервисов?
Есть вопросы на которые сложно найти решение?
Вы можете создать топик на нашем форуме и там описать сложность! (это бесплатно) Создать топик
Есть вопросы на которые сложно найти решение?
Вы можете создать топик на нашем форуме и там описать сложность! (это бесплатно) Создать топик
Ukrposhta integration with parcel statuses does not work correctly
1. "Return for the return address: for the destination address"
2. Return for the return address
these statuses are ignored. fix it
https://prnt.sc/u9io4i
https://prnt.sc/u9iqjc
Original question is available on version: ru
1. "Return for the return address: for the destination address"
2. Return for the return address
these statuses are ignored. fix it
https://prnt.sc/u9io4i
https://prnt.sc/u9iqjc
Answers:
Hello. When finalizing Ukrposhta, we were provided with a specific file with a list of statuses that the api can give. It can be supplemented with the necessary for 1 hour
07.09.2020, 17:46
Original comment available on version: ru
where do I provide it?
files are not attached.
and where processes are attached.
you don't want to talk to me.
https://prnt.sc/u9iqjc
files are not attached.
and where processes are attached.
you don't want to talk to me.
https://prnt.sc/u9iqjc
07.09.2020, 17:49
Original comment available on version: ru
You probably misread the message. When I did the integration with Ukrposhta, the author of the technical task gave me a specific list of Ukrposhta statuses that need to be added to the action. To add additional (which you are missing), you need 1 hour of refinement.
07.09.2020, 17:52
Original comment available on version: ru
so improve it. what is the problem?
I think you can add a new status faster.
I think you can add a new status faster.
07.09.2020, 17:55
Original comment available on version: ru
In the integration of Ukrposhta, a lot of statuses do not work out of two dozen, only three were found that work for our needs.
07.09.2020, 18:45
Original comment available on version: ru
You can provide a list of such statuses and pay for revision to add them. Cost of revision 1 hour.
08.09.2020, 14:12
Original comment available on version: ru
and with the next update everything will break again.
08.09.2020, 19:17
Original comment available on version: ru
http://prntscr.com/udrkzt
at least one of these two statuses is already in the directory.
must be processed.
and it is ignored by the integration.
at least one of these two statuses is already in the directory.
must be processed.
and it is ignored by the integration.
08.09.2020, 19:24
Original comment available on version: ru
Unfortunately, I can't help you without concrete examples. If you show me a bp in which there is an action and a process that had such a status before setting the action and switching to the stage did not happen - I can answer why. If it just doesn't work, I can't help.
09.09.2020, 09:48
Original comment available on version: ru
process 2634 for example as in the screenshot
20.10.2020, 13:09
Original comment available on version: ru
What date and at what stage do you think this process should have passed?
20.10.2020, 14:32
Original comment available on version: ru
20.10.2020, 15:15
Original comment available on version: ru
https://prnt.sc/v3q2ok as far as I can see, there is only information about one status in the comments. Perhaps due to the fact that the status change happened quickly, Ukrposhta could not give the parcel status at 17:00 via api. And at 18:00, when the kroner worked again, the mail had a different status (the status of the parcel is tracked by box once an hour). If you are not satisfied with the status update once an hour, you can set the action "Start the Ukrposhta tracking procedure" in the automation Once a minute and set it to 20 or 30 minutes so that Ukrposhta statuses are tracked more often.
21.10.2020, 13:18
Original comment available on version: ru
http://prntscr.com/v4tn4m
Like the statuses changed almost 50 minutes.
And it was supposed to work at 17:00.
chudnenko put 20 minutes.
Like the statuses changed almost 50 minutes.
And it was supposed to work at 17:00.
chudnenko put 20 minutes.
22.10.2020, 22:40
Original comment available on version: ru
between 16:55 (when the status appeared on the screen) and 17:00 (when the cron started) there are 5 minutes, I am not sure that at 17:00 the api was already giving a new status and not the old one and that the mail was second to second updates the statuses in the api and in the history where you watch them.
23.10.2020, 11:10
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
