Description
When a user proceeds without selecting a title, the application fails silently on the UI.
No validation message or error indication is shown to the user. Instead, the request results in a 500 Internal Server Error logged in the console, and the expected result page does not render. This creates a poor user experience and makes the issue difficult to understand from the frontend.
Steps to Reproduce
- Open the image transformation flow.
- Upload an image successfully.
- Do not select or enter a title.
- Trigger the action to proceed (e.g., generate/update image).
- Observe the behavior.
Expected Behavior
The application should validate the title field on the client side.
If the title is missing:
Alternatively, the backend should return a 4xx validation error with a meaningful message.
Actual Behavior
- No UI validation or error indication is shown.
- The expected result page does not appear.
- The browser console shows a 500 Internal Server Error.
- The failure is not communicated to the user.
Impact
- Users receive no feedback on why the action failed.
- Debugging becomes difficult due to lack of validation and error messaging.
- Backend is handling a preventable invalid request.
Screenshots

Description
When a user proceeds without selecting a title, the application fails silently on the UI.
No validation message or error indication is shown to the user. Instead, the request results in a 500 Internal Server Error logged in the console, and the expected result page does not render. This creates a poor user experience and makes the issue difficult to understand from the frontend.
Steps to Reproduce
Expected Behavior
The application should validate the title field on the client side.
If the title is missing:
Alternatively, the backend should return a 4xx validation error with a meaningful message.
Actual Behavior
Impact
Screenshots