# Bug OP-9651 - API notification error on work package query page

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | High |
| Module |  |
| Target versions | 12.1.5 |
| Observed in versions | 12.0.0 |
| Sprint | 12.1.5 |
| Backlog bucket |  |
| Bug found in version (deprecated) | 12.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 |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

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

## Costs

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

## Description

### **Environment**:

community

OP 12.0.4

### **Steps to reproduce:**

1.  (Not reliably reproducible but here is what I did):
2.  Navigate to project "OpenProject".
3.  Open query "OpenProject 12.0.5".
4.  Open work package in split screen.

### **Actual Behavior**

API error message shown (disappears on reload).

This error also appears on other pages (e.g. in notification center: <mention class="mention" data-id="40023" data-type="work_package" data-text="#40023">\#40023</mention>)

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/26027/content"></div></figure>

### **Expected Behavior**

The error message is non-critical and does not provide any useful information to the user.

  - Do not show error message in this case.
  - Continue showing a red badge on the notification bell, but remove the number displayed (since that number may no longer be accurate).

### Technical note

  - Locally this can reliably be reproduced by the following steps
    1.  Make sure to have a notification
    2.  Go to any page
    3.  Cancel the rails server
    4.  Wait on the page: After 10 seconds a new request is being sent to fetch new notifications, resulting in the error