medusajs/medusa

[Bug]: ProductModuleService updateProductOptionValues is a no-op

Open

#14878 opened on Mar 11, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)TypeScript (22,539 stars) (2,090 forks)batch import
good first issuetype: bugversion: 2.0

Description

Package.json file

{
  "dependencies": {
    "@medusajs/admin-sdk": "2.11.3",
    "@medusajs/cli": "2.11.3",
    "@medusajs/framework": "2.11.3",
    "@medusajs/js-sdk": "2.11.3",
    "@medusajs/medusa": "2.11.3",
    "@medusajs/types": "2.11.3",
  },
  "devDependencies": {
    "@medusajs/test-utils": "2.11.3",
  }
}

Node.js version

v20.19.2

Database and its version

PostgreSQL 18.3

Operating system name and version

Windows 11

Browser name

No response

What happened?

I called ProductModuleService.updateProductOptionValues. The second parameter, data gets overwritten by a medusa context because of code in the LocalWorkflow class:

https://github.com/medusajs/medusa/blob/c7e799d090934b63a951d39deb0aafecd811fd32/packages/core/orchestration/src/workflow/local-workflow.ts#L110-L134

Specifically, the issue is that MedusaService is assigning the updateProductOptionValues method in the same way as all other update methods, that is, having a context in the second argument (index 1), while updateProductOptionValues has it in the third argument (index 2):

https://github.com/medusajs/medusa/blob/c7e799d090934b63a951d39deb0aafecd811fd32/packages/core/utils/src/modules-sdk/medusa-service.ts#L202-L216

Expected behavior

Calling ProductModuleService.updateProductOptionValues will update the product option values.

Actual behavior

Any data input to ProductModuleService.updateProductOptionValues is dropped and a medusa context replaces it, effectively rendering the method a no-op.

Link to reproduction repo

https://github.com/medusajs/medusa

Contributor guide

Tech stack
typescriptnodejspostgresql
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptNode.jsUnderstanding of Medusa service pattern
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
The bug is in `packages/core/orchestration/src/workflow/local workflow.ts` lines 110-134 where the second parameter `data` gets overwritten by a medusa context. Additionally, `packages/core/utils/src/modules sdk/medusa service.ts` lines 202-216 assign the method with context in the second argument, but `updateProductOptionValues` expects it in the third. Investigate how `MedusaService` wraps methods and how `LocalWorkflow` handles arguments. Ensure the method's parameter signature is correctly aligned so that `data` is not replaced.