↓
Rivya AI Docs

Rivya Notifications: Account Events and Unread Notices

Review Rivya billing, credit and generation notices. Check current account records, follow related-page links and mark notifications as read.

Last reviewed on November 5, 2026

Open /notifications after signing in to review billing, credit and generation notices. Each notice records 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 the 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, credit and generation counts cover notices in the loaded list. They are not account balances, generation totals or lifetime event counts. A notice missing from this list does not mean the underlying record was deleted.

Choose the right follow-up

NoticeWhat to check next
Subscription started or renewedOpen billing settings to confirm the plan and renewal details.
Payment failedCheck the related billing record or checkout status before attempting another payment.
Credit package addedOpen credit settings and confirm the added credits and their expiry.
Generation succeededOpen generation history to find the result; save any file you need.
Generation failedInspect the task and any credit return before deciding whether to retry.
Insufficient creditsCheck your current spendable balance and the next request's estimate.

Use each card's related-page link. Generation notices can link to the task in History; other links may open a list or settings page. 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 displayed list. It can differ from the number of cards on screen. Each card shows Read or Unread. Opening its related page does not automatically mark the notice as read.

Use Mark all as read after reviewing the notices you need. This marks 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 button is disabled when there are no loaded notices or no unread notices, and while the request is in progress.

Read and unread describe whether notifications have been marked, not whether the underlying issue is resolved. If the action reports an error, refresh the page to check whether the notices were marked before trying again. The bell count may not update immediately; reopen or reload the notification page to check the 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 your 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 processing, timeout and failure states. 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. The dashboard preview is not the complete feed. Rivya groups repeated insufficient-credit generation notices by account and UTC date. Do not expect a 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 instead of 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 sign-in 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 sign-up is currently unavailable. Email preferences are separate from in-app read status; see Account settings for the current account controls.

For when to use notifications alongside History and settings, read Why Rivya has a notifications center.