# Bug OP-10816 - Show better error for dependent result for StoragesController Create action

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-10816

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 12.2.0 |
| Observed in versions |  |
| Sprint | 12.2.0 |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

Currently, if a dependent error occurs during storage creation, it is shown in the form for an attribute that does not exist in the form.

Better would be to just show that the model is invalid as a base error, to not confuse the user.
