Notifications “All” tab fails while filtered tabs work / 通知の「すべて」タブが動作せず、フィルタ付きのみ動作する

[arikantr]

Türkçe

Merhaba,

Kendi Misskey sunucumda (versiyon: 2025.8.0, adres: https://tiwit.tr) bildirimler sekmesinde bir hata yaşıyorum.

Sorun: “Tümü” sekmesi açıldığında “Bir hata oluştu – Tekrar dene” mesajı çıkıyor.

Detay: “Bahsetmeler” veya “Doğrudan notlar” gibi filtreler seçildiğinde bildirimler düzgün şekilde görüntüleniyor.

Tahmin: /api/notifications uç noktası çağrıldığında hata dönüyor ancak filtreli istekler (ör. mentions, direct notes) sorunsuz çalışıyor.

Ek bilgi: Loglarda API isteği sırasında hata kaydı görünüyor. Sorunun bildirim tablosundaki bozuk kayıt veya istemci tarafındaki sorgu parametrelerinden kaynaklanabileceğini düşünüyorum.

Lütfen inceleyebilir misiniz?

Teşekkürler.

---

English

Hello,

On my self-hosted Misskey server (version: 2025.8.0, address: https://tiwit.tr) I encounter an issue with the notifications page.

Problem: When opening the “All” tab under notifications, it only shows “An error occurred – Retry”.

Details: Filtered views such as “Mentions” or “Direct notes” work correctly and display notifications.

Possible cause: It seems that the /api/notifications endpoint fails when fetching all notifications, while filtered requests (e.g. mentions, direct notes) succeed.

Additional info: Server logs indicate an error during this API call. It might be caused by corrupted records in the notifications table or mismatched parameters in the client request.

Could you please take a look at this?

Thanks.

---

日本語 (Japanese)

こんにちは。

自分の Misskey サーバー（バージョン: 2025.8.0、アドレス: https://tiwit.tr）で通知ページに問題が発生しています。

問題: 通知の「すべて」タブを開くと 「エラーが発生しました – 再試行」 というメッセージしか表示されません。

詳細: 「言及」や「ダイレクトノート」などフィルタを選択した場合は、正常に通知が表示されます。

原因の可能性: /api/notifications エンドポイントで全件取得する際にエラーが発生し、フィルタ付きリクエスト（言及、ダイレクトなど）は正常に処理されているようです。

追加情報: サーバーログには API 呼び出し時のエラーが出ています。通知テーブル内の不正データ、またはフロントエンドのパラメータ処理に問題がある可能性があります。

ご確認いただけますでしょうか。

よろしくお願いします。

[arikantr]

Summary:
On my self-hosted Misskey instance, the “All/Grouped” notifications view fails with “An error occurred – Retry”. Filtered views (e.g., Mentions/DM) usually work. Server logs show MiRole not found during i/notifications-grouped.

Environment:

Version: 2025.8.0

Instance: https://tiwit.tr/

Setup: Docker (PostgreSQL + Redis)

Steps to Reproduce:

Open the notifications page.

Switch to the “All” or “Grouped” tab.

The client shows “An error occurred – Retry”.

Actual Behavior:

Backend endpoint i/notifications-grouped returns 500 / Internal error.

Expected Behavior:

The “All/Grouped” notifications should load without errors; even if a referenced role is missing, the page should still return partial results gracefully.

Relevant Log (trimmed):

ERR [api] Internal error occurred in i/notifications-grouped: Could not find any entity of type "MiRole" matching: {
    "id": "ac9e0svhzjq302gu"
}
ep: 'i/notifications-grouped',
ps: { limit: 20, allowPartial: true, markAsRead: true, i: '...' }
e: {
  message: 'Could not find any entity of type "MiRole" matching: {"id":"ac9e0svhzjq302gu"}',
  code: 'EntityNotFoundError',
  stack: '... RoleEntityService.pack ... NotificationEntityService.packGroupedMany ...'
}

Impact:

The “All/Grouped” notifications view becomes unusable. Users can only see notifications via some filtered tabs.

Workaround:

Manually deleting notifications that reference a deleted/missing role temporarily fixes the issue (DB cleanup).

Proposed Fix:

Add graceful fallback in RoleEntityService.pack and/or NotificationEntityService.pack*:

If the referenced MiRole is missing, skip that notification (or pack with null/placeholder) and return partial results instead of throwing 500.

Thanks!