# Bug OP-17389 - Missing/wrong error handling for asynchronous dialogs

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module | Frontend components and Primer design system |
| Target versions | 16.2.0 |
| Observed in versions | 16.0.0 |
| Sprint | 16.2.0 |
| Backlog bucket |  |
| Bug found in version (deprecated) | 16.0.x |
| 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 | Jan Sandbrink |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

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

## Costs

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

## Description

### Steps to reproduce

1.  Perform an action that would render an `async-dialog`, e.g. deleting an item from a hierarchy custom field
    
2.  Wait for the web server to return an unexpected errorneous response (e.g. an HTTP 502 or similar)
    
    1.  In development this can be provoked by introducing an error to the corresponding response action
        
    2.  on a real instance/QA:
        
        1.  Set a session timeout in administration auth settings and wait for timeout to occur (put browser tab into background)
            
        2.  or delete your session cookie
            

### What is the buggy behavior?

The entirety of the returned response body is appended to the page as HTML

### What is the expected behavior?

*   No persistent changes to the page layout in unexpected locations
    
*   Optionally: An error message or indicator that something went wrong
