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.

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

Error when cancelling a delivered fulfilment #2335

Closed
skid opened this issue Aug 4, 2023 · 2 comments
Closed

Error when cancelling a delivered fulfilment #2335

skid opened this issue Aug 4, 2023 · 2 comments
Assignees
Labels
type: bug 🐛 Something isn't working

Comments

@skid
Copy link
Contributor

skid commented Aug 4, 2023

Describe the bug
The following error happens on the server when I try to cancel a fulfillment that's been marked as delivered:

Error: error.entity-with-id-not-found
    at TransactionalConnection.getEntityOrThrowInternal (node_modules/@vendure/core/src/connection/transactional-connection.ts:261:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at StockMovementService.createAllocationsForOrderLines (node_modules/@vendure/core/src/service/services/stock-movement.service.ts:163:31)
    at Object.onTransitionEnd (node_modules/@vendure/core/src/config/fulfillment/default-fulfillment-process.ts:95:13)
    at awaitPromiseOrObservable 

This happens on a migrated database (1.9.7 -> 2.0.4) - haven't tried it on a fresh 2.0.4 database.

To Reproduce
Steps to reproduce the behavior:

  1. Create an order, a fulfillment and mark the fulfillment as delivered
  2. Try to cancel the fulfillment

Expected behavior
The fulfillment should be cancelled.

Environment (please complete the following information):

  • @vendure/core version: 2.0.4
  • Nodejs version 16
  • Database (mysql/postgres etc): Postres 15
@skid skid added the type: bug 🐛 Something isn't working label Aug 4, 2023
@michaelbromley michaelbromley moved this to 📋 Backlog in Vendure OS Roadmap Aug 4, 2023
@michaelbromley
Copy link
Member

Hi,

I tried to reproduce in the current master branch with freshly-populated data and do not get the error. So for you does this also occur with newly-created orders, and not just orders migrated from v1?

@michaelbromley
Copy link
Member

Actually I think this might be the same a #2306, which was fixed in v2.0.5

@michaelbromley michaelbromley moved this from 📋 Backlog to ✅ Done in Vendure OS Roadmap Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug 🐛 Something isn't working
Projects
Status: 🚀 Shipped
Development

No branches or pull requests

2 participants