Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: some shipments have no myparcel status #571

Merged
merged 2 commits into from
Jun 4, 2021
Merged

fix: some shipments have no myparcel status #571

merged 2 commits into from
Jun 4, 2021

Conversation

RichardPerdaan
Copy link
Member

  • because some orders will not be sent with myparcel, they has no myparcel status. In some cases, a magento shipment has been made and will cause errors

@RichardPerdaan
fix: some shipments have no myparcel status
10e09b5 
- because some orders will not be sent with myparcel, they has no myparcel status. In some cases, a magento shipment has been made and will cause errors
@RichardPerdaan RichardPerdaan requested a review from a team June 2, 2021 18:36
joerivanveen
joerivanveen approved these changes Jun 3, 2021
View reviewed changes
Copy link
Contributor

@joerivanveen joerivanveen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Zie mijn opmerking, maar los daarvan lijkt me dit werkend. :-)

@RichardPerdaan RichardPerdaan merged commit 56da20b into develop Jun 4, 2021
@RichardPerdaan RichardPerdaan deleted the MY-28716-multipe-error-from-cronjob branch June 4, 2021 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@joerivanveen joerivanveen joerivanveen approved these changes

@EdieLemoine EdieLemoine EdieLemoine approved these changes

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@RichardPerdaan @EdieLemoine @joerivanveen