Getting success message after sending invalid SKU for the inventory/source-items API

[webgility-amazonapi]

Preconditions and environment

• Magento version -> 2.3.0
• here is the api details curl --location 'http://php72.webgility.com/magento230_test/rest/V1/inventory/source-items' \ --header 'Authorization: Bearer mbngyhiyvqpbaqq2b1d87onkf686nojp' \ --header 'Content-Type: application/json' \ --header 'Cookie: PHPSESSID=k60cb85fp23no9aeuqef9v10bd' \ --data '{ "sourceItems": [ { "sku": "dgdfgdxfgdfgd", "source_code": "default", "quantity": 0, "status": 1 } ] }

Also, the SKU used in the above request is not added to the store.

Steps to reproduce

• enter the data in the request body • send incorrect SKU Observe that API is giving 200 status code even the SKU is not existing on the particular store.

Expected result

It should give the error message for the incorrect SKU.

Actual result

API is sending 200 status code .

Additional information

No response

Release note

No response

Triage and priority

• [X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @webgility-amazonapi. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://b00a45329bc5fdc540fb1bcb63a45f5e.instances-prod.magento-community.engineering Admin access: https://b00a45329bc5fdc540fb1bcb63a45f5e.instances-prod.magento-community.engineering/admin_af12 Login: 29232832 Password: c593053f6e1e

[engcom-Bravo]

Hi @webgility-amazonapi,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

• • enter the data in the request body
• • send incorrect SKU

We are getting success message while sending invalid SKU.Since product is not there in that store it should give error but it is giving 200 OK response.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-10523 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[zia1177]

@magento I am working on this

[m2-assistant[bot]]

Hi @zia1177! :wave: Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[zia1177]

@magento add to contributors team

[m2-assistant[bot]]

Hi @zia1177! :wave: Thank you for joining. Please accept team invitation :point_right: here :point_left: and add your comment one more time.

[zia1177]

@magento I am working on this