[bug]: Notification list endpoint 404s due to missing trailing slash in frontend service call

[cmc-mfino]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Describe the bug

The workspace inbox shows the correct unread notification count (badge), but the actual notification list never loads — the inbox stays on the empty-state illustration even though notifications exist.

Root cause

WorkspaceNotificationService.list() in packages/services/src/workspace/notification.service.ts builds its request URL without a trailing slash:

async list(workspaceSlug, params) {
  return this.get(`/api/workspaces/${workspaceSlug}/users/notifications`, { params })
  ...
}

Every sibling method in the same file (getUnreadCount, update, markAsRead, archive, markAllAsRead) correctly appends a trailing slash — only .list() omits it.

The backend only registers this route with a trailing slash:

# apps/api/plane/app/urls/notification.py
path(
    "workspaces/<str:slug>/users/notifications/",
    NotificationViewSet.as_view({"get": "list"}),
    name="notifications",
),

So the request 404s at the Django routing layer. In our self-hosted deployment (Traefik reverse proxy), this upstream 404 surfaces to the browser as a 500, which obscured the real cause until we checked the API pod logs directly.

Confirmed affected versions

• v1.2.0
• v1.3.1
• preview branch (current HEAD as of 2026-07-28) — bug is still present

Steps to reproduce

Steps to reproduce

1. Have User A mention/comment-tag User B on a work item
2. As User B, open the workspace inbox
3. Inbox badge shows unread count correctly
4. Notification list panel remains empty; network tab shows a failed request to /api/workspaces/{slug}/users/notifications?... (no trailing slash)

Expected behavior

The notification list request should include the trailing slash (matching every other method in the same service file), or the backend should register both slash and non-slash variants.

Suggested fix

One-line change in packages/services/src/workspace/notification.service.ts:

- return this.get(`/api/workspaces/${workspaceSlug}/users/notifications`, { params })
+ return this.get(`/api/workspaces/${workspaceSlug}/users/notifications/`, { params })

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

v1.2.0

[makeplane]

Synced with Plane Workspace 🔄

[GIT-289] [bug]: Notification list endpoint 404s due to missing trailing slash in frontend service call

[cmc-mfino]

Workaround: Notification List Not Loading (Traefik Reverse Proxy)

Symptom

• The workspace inbox badge shows the correct unread notification count.
• The notification list itself never loads — the inbox stays on the empty-state illustration even though notifications exist.
• Browser network tab shows a failed request to /api/workspaces/{slug}/users/notifications?....

Root Cause

WorkspaceNotificationService.list() in packages/services/src/workspace/notification.service.ts builds its request URL without a trailing slash:

async list(workspaceSlug, params) {
  return this.get(`/api/workspaces/${workspaceSlug}/users/notifications`, { params })
  // missing trailing slash ^
}

Every sibling method in the same file (getUnreadCount, update, markAsRead, archive, markAllAsRead) correctly appends a trailing slash — only .list() omits it.

The backend only registers this route with a trailing slash:

# apps/api/plane/app/urls/notification.py
path(
    "workspaces/<str:slug>/users/notifications/",
    NotificationViewSet.as_view({"get": "list"}),
    name="notifications",
),

So the request 404s at the Django routing layer. Depending on your reverse proxy, this may surface to the browser as a 404 or a generic 500.

Confirmed affected versions: v1.2.0, v1.3.1, and the preview branch (still present as of this writing).

Workaround (Traefik reverse proxy users)

If you're running Plane behind Traefik, you can patch around this until it's fixed upstream by rewriting the path server-side.

1. Create a Middleware resource

apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
  name: plane-notifications-slash-fix
  namespace: <your-namespace>
spec:
  replacePathRegex:
    regex: "^/api/workspaces/([^/]+)/users/notifications$"
    replacement: "/api/workspaces/$1/users/notifications/"

kubectl apply -f plane-notifications-slash-fix.yaml

2. Attach it to your /api route

Attach it alongside any existing middlewares on the route that matches PathPrefix(/api). Example patch if you're using an IngressRoute:

kubectl patch ingressroute <your-ingressroute-name> -n <your-namespace> --type='json' \
  -p='[{"op": "add", "path": "/spec/routes/<index-of-api-route>/middlewares/-", "value": {"name": "plane-notifications-slash-fix"}}]'

Replace <index-of-api-route> with whichever route entry matches PathPrefix(/api) in your IngressRoute spec.

3. Verify

kubectl get ingressroute <your-ingressroute-name> -n <your-namespace> -o yaml | grep -A 6 "PathPrefix(\`/api\`)"

You should see plane-notifications-slash-fix listed under that route's middlewares.

Note: If your IngressRoute is Helm-managed (as it is with the official Plane Helm chart), this middleware attachment will be wiped on the next helm upgrade and needs to be reapplied — same as any other manual patch to a Helm-templated resource.

For nginx-ingress or Caddy Users

The equivalent fix is a path rewrite rule mapping:

/api/workspaces/{slug}/users/notifications   (no trailing slash, any query string)

to the same path with a trailing slash appended, before the request hits the Plane backend.

Suggested Upstream Fix

One-line change in packages/services/src/workspace/notification.service.ts:

- return this.get(`/api/workspaces/${workspaceSlug}/users/notifications`, { params })
+ return this.get(`/api/workspaces/${workspaceSlug}/users/notifications/`, { params })

[misterkuka]

Confirmed on self-hosted CE (additional repro)

• Version: plane-backend + plane-frontend v1.3.1 (also confirmed still broken on v1.4.0 / preview package sources)
• Deployment: Kubernetes + Traefik

Behaviour

Request	Result
GET /api/workspaces/{slug}/users/notifications?… (no trailing slash)	API logs 404 (0–4ms); browser/Traefik often surfaces 500 Internal Server Error
GET /api/workspaces/{slug}/users/notifications/?… (with trailing slash)	200 + paginated results
GET …/notifications/unread/	200 (badge works)

So the inbox badge works, but the notification list never loads — same root cause as described here.

Frontend still wrong on v1.4.0

// packages/services/src/workspace/notification.service.ts  (v1.4.0 tag)
return this.get(`/api/workspaces/${workspaceSlug}/users/notifications`, { params })
// missing trailing slash; every sibling method has one

// apps/web/core/services/workspace-notification.service.ts  (same)
await this.get(`/api/workspaces/${workspaceSlug}/users/notifications`, { params })

Suggested one-line fix in both service files (append / before query params) still applies. Happy to open a PR if maintainers want it.

[misterkuka]

Opened a one-line fix PR (both service copies): #9521

Still broken on v1.4.0 / preview until that (or equivalent) lands.