APIs throwing 500 status when 4** is expected

[pyarun]

Describe the bug
When trying to delete a non-existing workflow using DELETE {{conductorBaseUrl}}/api/metadata/workflow/:name/:version api
replies back with 500 status code.

{
    "status": 500,
    "message": "No such workflow definition: memes_maker version: 2",
    "instance": "1a79daf01f84",
    "retryable": false
}

Details
Conductor version: v3.19.0
Persistence implementation: Postgres
Queue implementation: Postgres
Lock: I guess redis

To Reproduce
Steps to reproduce the behavior:

1. Use API to delete non existing workflow

curl --location --request DELETE 'http://localhost8080/api/metadata/workflow/memes_maker/2' 

2. See error

Expected behavior
Status code should be 404

Additional context
Same thing happens if we try to create existing workflow with existing version.

[v1r3n]

Hi @pyarun are you using postgres as a backend?

[pyarun]

Hi @pyarun are you using postgres as a backend?

yes

[prathamjagga]

In both postgres and redis, NotFoundException is thrown, but in the redis the API gives 4XX error code. need to look what is happening wrong here.

[shrimank]

Same issue I am checking in latest version v3.21.6, expected 404 receiving 500 Http status code
#bug

[jeffbulltech]

👋 Hi @pyarun @prathamjagga @shrimank

We're currently reviewing open issues in the Conductor OSS backlog, and noticed that this issue hasn't been addressed.

To help us keep the backlog focused and actionable, we’d love your input:

• Is this issue still relevant?
• Has the problem been resolved in the latest version v3.21.12?
• Do you have any additional context or updates to provide?

If we don’t hear back in the next 14 days, we’ll assume this issue is no longer active and will close it for housekeeping. Of course, if it's still a valid issue, just let us know and we’ll keep it open!

Thanks for contributing to Conductor OSS! We appreciate your support. 🙌

Jeff Bull

Developer Community Manager | Orkes

DM on Conductor Slack
Email me!

[pyarun]

Still same on version 3.21.4 and 3.21.12

[jeffbulltech]

Still same on version 3.21.4 and 3.21.12

Thanks for letting me know @pyarun I'll make sure this is added to our roadmap.