> 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/notification-types.md). # Notification Types Every notification is either an ongoing problem, which stays open until it's fixed, or a one-time event, which tells you something happened. This page lists each one, what it means and what to do. ### Ongoing problems These stay open until the underlying issue clears, then resolve on their own. | Notification | What it means | Where it appears | What to do | Clears when | | ---------------------------------------------- | --------------------------------------------------------------------------------------- | ---------------- | --------------------------------------------------------------------- | ------------------------------ | | **Reconnect needed** | An integration's saved credentials expired or access was removed. | Needs you | **Reauthorize** | The integration works again. | | **Couldn't reach the source** (credentials) | Daasity couldn't log in to the source. | Needs you | **Check connection** for databases, **Reauthorize** for other sources | The integration works again. | | **Couldn't reach the source** (permissions) | Daasity connected but isn't allowed to read the data. | Needs you | **Reauthorize** | The integration works again. | | **Couldn't reach the source** (configuration) | Something in the integration's setup is wrong, such as a missing report or a setting. | Needs you | **Review** | The integration works again. | | **Couldn't reach the source** (unknown reason) | The connection check failed and the cause isn't clear yet. Daasity investigates. | We're on it | Nothing. **Review** shows the details. | The integration works again. | | **Sheet didn't load** | A sheet was renamed, moved, re-shared or its columns changed. | Needs you | **Review** | The sheet loads successfully. | | **YML Definition Changed** | The file an integration was built from no longer matches the repository. | Needs you | **Review** | The integration works again. | | **Vendor issue** | The source platform had a problem on its side, so Daasity skipped that portion of data. | We're on it | Nothing | The next successful data pull. | Problems that stop recurring also close on their own. Login and connection problems close after 7 quiet days, once the integration has refreshed successfully. Sheet problems and vendor issues close after 14 quiet days. ### One-time events These appear in **Recent** for 7 days, or until you click **Dismiss**. | Notification | What it means | What to do | | ------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------------- | | **Some data was skipped** | A data refresh finished, but some of the data couldn't be pulled. | **Review** to see what was skipped and why. | | **Backfill didn't finish** | A history load failed. | **Reload history** | | **File couldn't be loaded** | A file sent by email or webhook couldn't be processed. | **View file** | | **Reports may be stale** | A transformation or data model failed to run, so some reports may not have the latest data. | **Review** | | **Integration paused** | Daasity Support paused an integration because of a problem on the source platform's side. | **Review** | | **Report Quota Exceeded** | The source platform's report quota ran out. Daasity switched to a full download instead. | Nothing | | **Report Stalled at Source** | A report sat in the source platform's queue too long. That period is filled in on a later refresh. | Nothing | | **TikTok Report Field Changed** | TikTok changed a field in one of its reports. | **Review** | ### Need help? If a notification doesn't clear after you've taken the suggested action, contact .