Rivya Notifications: Events, Unread Counts and Actions
Find Rivya billing, credit and generation notices, understand the 60-item feed and unread count, and open the right page to check or resolve an event.
Last reviewed on September 8, 2026
Open /notifications after signing in to review recorded billing, credit and generation events. A notification describes an event at a particular time; check the linked account or task page for its current state before paying or generating again.
Open the Notification Center
Use the notification bell or open /notifications directly. The bell shows an unread count, capped visually at 9+. The Dashboard previews the 4 most recent notices, while the full page loads the 60 most recent, newest first. There are currently no controls for older pages or category filtering.
The billing, credits and generation totals count notices within the loaded list. They are not account balances, generation totals or lifetime event counts. An older notice missing from the list is not proof that the underlying record was deleted.
Choose the Right Follow-up
| Notice | What to check next |
|---|---|
| Subscription started or renewed | Open billing settings to confirm the plan and renewal details. |
| Payment failed | Check the related billing record or checkout status before attempting another payment. |
| Credit package added | Open credit settings and confirm the added credits and their expiry. |
| Generation succeeded | Open generation history to find the result; save any file you need. |
| Generation failed | Inspect the task and any credit return before deciding whether to retry. |
| Insufficient credits | Check your current spendable balance and the next request's estimate. |
Use each card's related-page link. It may open a list or settings page rather than a specific task. Match the notice's model, date and event details with the relevant record. History and Task Lifecycle explain how to inspect generated work; Failed Tasks and Credit Refunds covers retries and returns.
Understand the Unread Count
The unread count covers the account's notifications, including ones outside the latest 60 shown. It can therefore differ from the number of cards on screen. The current feed does not label each card individually as read or unread, and opening a related page does not automatically mark the notice read.
Use Mark all read after reviewing the notices you need. This updates all notifications in the account, including older ones outside the displayed list. It does not delete notices, resolve failed tasks, change credit balances, pay invoices or cancel subscriptions. The action is unavailable when there are no loaded notices or no unread notices.
Read and unread describe whether notifications have been marked, not whether the underlying issue is resolved. The bell count may not change immediately; reopen or reload the notification page to check the updated total.
Check Billing and Credits at the Source
A notice about added credits records an earlier event, not the amount you can still spend. Credits may have been consumed or expired since then. The amounts in an insufficient-credit notice also describe that earlier attempt. Check /settings/credits for current balance and transactions; see Credits and Billing.
A failed-payment notice may remain after the payment issue is resolved. Check /settings/billing and the original checkout result before paying again. Payment Checkout explains how to distinguish processing, timeout and failure. A notification is not an invoice or a replacement for payment records.
If a Notice Is Missing or Looks Outdated
Check that you are in the correct account, then reload the full page. Do not use the four-item dashboard preview as the complete feed. Some repeated events are grouped: insufficient-credit generation notices are limited to one per account per UTC date. Do not expect one notice for every attempt, every chat message, or every low-balance change.
A missing notification alone does not prove that a task failed, a payment failed or credits were not added. Check the original generation page, history, billing or credit transactions as appropriate. If they disagree with an older notice, use the current record to decide your next step rather than resubmitting just to create a new notification.
If the state remains unclear, contact [email protected] with your account email, the notice's date and wording, the model or plan, and the task, checkout or invoice reference if available. Include the exact error; do not send login codes, API keys or full card details. See Troubleshooting.
Keep In-app Notices Separate from Email Preferences
The notification center is an in-app event feed. It does not promise an email or browser push alert for every event. Newsletter preferences are managed separately in account settings and do not mark in-app notices as read. See Account Settings.
For when to use notifications alongside history and settings, read Why Rivya Has a Notifications Center.