Update schedule registration API to return error codes for invalid requests#2278
Merged
cb-github-robot merged 1 commit intocloud-barista:mainfrom Jan 20, 2026
Merged
Conversation
…on errors in REST API
Member
|
/approve |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR modifies the schedule job registration API to return an explicit error code (
HTTP 422 Unprocessable Entity) instead of200 OKwhen validation fails.Why
Previously, the updated registration logic was applied only to the direct Registration API and was not reflected in the Job Scheduling flow.
Consequently, the scheduler returned
200 OKeven when validation errors occurred, failing to signal the error to the client.Impact
This change ensures that the client (Map UI) can instantly catch validation errors (e.g., invalid resource combinations) and display an error message to the user.
Updates to the Map UI to accommodate this change are planned to follow immediately.