fix(frontend): surface validate timeout error message instead of 503#55
Merged
ilramdhan merged 1 commit intoJun 28, 2026
Merged
Conversation
BFF validate route now returns 422 with base.message when finance service returns isSuccess=false (e.g. timeout on large file). validateBulkProductRoutingFile reads base.message from error responses so the toast shows the backend's readable message rather than "Validation failed: 503". Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
github-project-automation
Bot
moved this from Todo
to Done
in Goapps Roadmap [Frontend]
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
1 participant
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.
BFF validate route now returns 422 with base.message when finance service returns isSuccess=false (e.g. timeout on large file). validateBulkProductRoutingFile reads base.message from error responses so the toast shows the backend's readable message rather than "Validation failed: 503".
Description
Type of Change
Module/Component Affected
Changes Made
Related Issues
Fixes #
Related to #
Screenshots
Before
After
Testing Performed
Manual Testing
Browser Testing
Build Verification
npm run lintpassesnpx tsc --noEmitpassesnpm run buildsucceedsAccessibility
Performance
Pre-merge Checklist
Reviewer Notes