Error in cron_schedule for job myparcel_update_status

[gerben86]

Plugin version

4.5.0

Magento version

2.4.4

PHP version

7.4.30

What went wrong?

After updating to Magento 2.4.4 and the latest MyParcel-plugin there are errors in the cron_schedule table for the job: myparcel_update_status:

Error:
"0 - - Unknown error: {\"code\":0}. Please contact MyParcel."

Printscreen:

The error says that I need to contact MyParcel, so here's the ticket :)
Could you let me know how I can prevent those errors?
I get 1 error every 15 minutes.

Reproduction steps

Run the cron-job of Magento and have the MyParcel plugin installed.

Relevant log output

No response

Additional context

No response

[AlexNauta]

I have the same issue here with
Magento 2.4.3-p1
MyParcel version 4.5.0

[joerivanveen]

We are currently investigating this issue.

[gerben86]

We are currently investigating this issue.

I got this information from info@myparcel.nl, do you think that could solve the issue?:
Zou je wellicht een nieuwe API key willen generen in de myparcel back office en deze dan plaatsen in jouw Magento 2 shop?

It looks like that that did the trick:

But now I still have a lot of orders in the backend with the wrong shipping status (still 'Voorgemeld' instead of 'Afgeleverd'). How can I update all those statusses?

[RichardPerdaan]

When you use the command php bin/magento cron:run it will retrigger the actions to get the shipping status.

[gerben86]

Thanks! That will indeed trigger the cron. But I have orders which are delivered on 24-6, but the status in Magento is still ‘Voorgemeld’. They are shipped with the previous version of the MyParcel plug-in. Due to the age of the order it won’t be update via the cron anymore. How can we update the shipment status of those old orders? Op do 7 jul. 2022 om 15:39 schreef Richard Perdaan ***@***.***

…

When you use the command php bin/magento cron:run it will retrigger the actions to get the shipping status. — Reply to this email directly, view it on GitHub <#697 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEFLJSR2Q5AVXHFBIFDGJ23VS3MYBANCNFSM5Z2EJSNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[gerben86]

Thanks! That will indeed trigger the cron. But I have orders which are delivered on 24-6, but the status in Magento is still ‘Voorgemeld’. They are shipped with the previous version of the MyParcel plug-in. Due to the age of the order it won’t be update via the cron anymore. How can we update the shipment status of those old orders? Op do 7 jul. 2022 om 15:39 schreef Richard Perdaan @.***
…
When you use the command php bin/magento cron:run it will retrigger the actions to get the shipping status. — Reply to this email directly, view it on GitHub <#697 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFLJSR2Q5AVXHFBIFDGJ23VS3MYBANCNFSM5Z2EJSNA . You are receiving this because you authored the thread.Message ID: @.***>

Also new orders stay at the shipping status 'Voorgemeld', so I'm not able to trace the shipment in the Magento admin anymore...

[joerivanveen]

Can you check your system.log file for the message 'Orderbeheer: no orders updated [] []', based on whether that is present we will be able to determine next steps.

[gerben86]

When I'm back from holidays I'll check this. Op vr 22 jul. 2022 om 16:46 schreef Joeri van Veen ***@***.***

…

: Can you check your system.log file for the message 'Orderbeheer: no orders updated [] []', based on whether that is present we will be able to determine next steps. — Reply to this email directly, view it on GitHub <#697 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEFLJSXUXI4BOM7KIO35LC3VVKX2VANCNFSM5Z2EJSNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[gerben86]

Hi,

This is what I see in the cron.log:
`[2022-08-04T20:15:05.927050+00:00] main.INFO: Cron Job myparcel_update_status is run [] []

[2022-08-04T20:15:06.554054+00:00] main.INFO: Cron Job myparcel_update_status is successfully finished. Statistics: {"sum":0.6269519329071,"count":1,"realmem":0,"emalloc":613072,"realmem_start":113246208,"emalloc_start":64227368} [] []`

This is in the system.log:
[2022-08-04T20:15:06.521732+00:00] main.NOTICE: Orderbeheer: no orders updated [] []

[gerben86]

Any update on this?
Still all my shipments have the status 'Voorgemeld' instead of 'Afgeleverd'.

[gerben86]

@RichardPerdaan : Any update on this? Still all my shipments have the status 'Voorgemeld' instead of 'Afgeleverd'.

[RichardPerdaan]

Solved in 4.6.1 of the MyParcel plugin