> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/technical-docs/notification-center/notifications-faq.md).

# Notifications FAQ

Answers to the questions we hear most about the Notification Center.

### What changed from the old notifications?

|                                    | Before                                               | Now                                                                                 |
| ---------------------------------- | ---------------------------------------------------- | ----------------------------------------------------------------------------------- |
| A problem that repeats every day   | A new notification and a new email each time         | One notification that updates ("Seen 12 times") and one email for the whole problem |
| When the problem is fixed          | Stayed open until someone clicked **Mark as solved** | Closes on its own and moves to **Resolved** with the reason                         |
| How notifications are listed       | One list                                             | Grouped by who needs to act: **Needs you**, **We're on it** and **Recent**          |
| What to do next                    | Not always clear                                     | Each notification has one button for the next step                                  |
| Problems left open for a long time | Stayed in the list and on the bell                   | Move to **Older** after 30 days and stop counting toward the bell                   |

### Where did my old notifications go?

When the Notification Center launched, every open notification from the old system was closed with the reason **Cleared when notifications were upgraded**. You can see them under **Resolved** on the **All** tab for 30 days.

Nothing was lost. Any problem that is still happening opens again as a new notification.

### Do I need to mark a notification as solved?

No. The **Mark as solved** button is gone. An ongoing problem closes on its own when the integration works again.

### I clicked Got it. Why is the notification still there?

**Got it** means you've seen it. It takes the notification off the bell's count, but the notification stays visible until the problem itself is fixed.

### What does the number on the bell count?

Notifications in **Needs you** that nobody has clicked **Got it** on. Notifications in **Older**, **We're on it** and **Recent** don't count.

### Why is a new notification already under Older?

A problem moves to **Older** when its integration hasn't refreshed successfully in more than 30 days. If an integration has been failing for a long time, a new notification about it goes straight to **Older**. You can still act on it there.

### A notification says Daasity is on it. Do I need to do anything?

No. Notifications under **We're on it** are problems on Daasity's side or the source platform's side. They clear when the problem is fixed.

### Why didn't I get an email?

The most common reasons:

* **You were already emailed.** An ongoing problem sends one email when it first appears. Repeats update the notification in the app without another email.
* **Email notifications aren't turned on for your user.** See the Email Notifications page.
* **The notification type never emails.** **Vendor issue** and **Backfill didn't finish** show in the app only.
* **The integration hasn't refreshed successfully in more than 90 days.** Its notifications still appear in the app, but don't send emails.
* **It was a "Some data was skipped" notification.** These email at most once per day for each data refresh. They don't email at all when everything skipped was caused by a login problem, because **Reconnect needed** has already told you.
* **It was a "Reports may be stale" notification.** These email only if you manage your own transformation code.

### Why did I get another email about the same problem?

If a problem clears and then comes back, it counts as a new problem and sends a new email. An integration that switches back and forth between two different errors can send an email each time it switches.

### What do the slash and the orange dot on the bell mean?

* **A muted bell with a slash** means notifications are turned off for your account. Admins can turn them on from the bell. Other users can contact support.
* **An orange dot** means notifications are on, but no one is set to receive emails. Click **Choose recipients** to fix that.

### Who can act on a notification?

Everyone on your account can see every notification. All users can **Reauthorize** and **Check connection**. Other buttons are not available to entry-level users, who should ask an admin on the account or contact support.

### Still stuck?

Contact <support@daasity.com>.
