Description
While working on #227 (replacing browser alerts with toast notifications), I spent some time reviewing how errors are currently handled across the admin panel.
During that review, I noticed that there are several places where failed operations are only logged using console.error(). In these cases, developers can see the error in the browser console, but the user receives little or no indication that the action failed.
Current Behavior
When certain admin actions fail, the error is logged for debugging purposes, but no visible feedback is shown to the user.
This can create situations where a user clicks an action such as save, update, delete, upload, export, or similar operations and is left unsure whether the request succeeded, failed, or is still processing.
Why This Matters
The project already uses toast notifications in multiple areas and Issue #227 improved consistency by replacing the remaining browser alerts.
However, there are still workflows where failures are only reported through console logs, resulting in inconsistent user feedback across the admin experience.
Expected Behavior
When a user triggered operation fails, the application should provide clear and consistent feedback using the existing notification system while still preserving console logs for debugging.
This would help users immediately understand that an action was unsuccessful instead of relying on browser developer tools to identify the problem.
Additional Context
This issue was discovered while reviewing error handling patterns during work on #227.
Unlike #227, which focused on replacing browser alerts, this issue focuses on admin workflows where failed operations currently provide no user facing feedback.
Description
While working on #227 (replacing browser alerts with toast notifications), I spent some time reviewing how errors are currently handled across the admin panel.
During that review, I noticed that there are several places where failed operations are only logged using
console.error(). In these cases, developers can see the error in the browser console, but the user receives little or no indication that the action failed.Current Behavior
When certain admin actions fail, the error is logged for debugging purposes, but no visible feedback is shown to the user.
This can create situations where a user clicks an action such as save, update, delete, upload, export, or similar operations and is left unsure whether the request succeeded, failed, or is still processing.
Why This Matters
The project already uses toast notifications in multiple areas and Issue #227 improved consistency by replacing the remaining browser alerts.
However, there are still workflows where failures are only reported through console logs, resulting in inconsistent user feedback across the admin experience.
Expected Behavior
When a user triggered operation fails, the application should provide clear and consistent feedback using the existing notification system while still preserving console logs for debugging.
This would help users immediately understand that an action was unsuccessful instead of relying on browser developer tools to identify the problem.
Additional Context
This issue was discovered while reviewing error handling patterns during work on #227.
Unlike #227, which focused on replacing browser alerts, this issue focuses on admin workflows where failed operations currently provide no user facing feedback.