Skip to content

Gracefully skip notifications when company has no clients for message channel - #1401

Closed
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/por-22481-cursor-automated-triage-response-5541
Closed

Gracefully skip notifications when company has no clients for message channel#1401
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/por-22481-cursor-automated-triage-response-5541

Conversation

@cursor

@cursor cursor Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Handles a Copilot platform not_found response when creating in-product notifications for company-assigned tasks whose company has no client users (message channel cannot be created). This error was surfacing in Sentry as production noise from tasks-app notification paths.

Changes

  • Add isNoCompanyClientsMessageChannelError helper in copilotError.ts (mirrors existing senderCompanyId handling).
  • Skip notification fan-out when recipientIds is empty in createBulkNotification and company task assignment flow.
  • Gracefully skip in-product notification dispatch across NotificationService, grouped-email jobs, reply notifications, and validate-count backfill.
  • Add unit tests for the new error detection and notification skip behavior.

Manual verification

  • yarn test src/utils/copilotError.test.ts src/app/api/notification/notification.service.test.ts — all passing.

Linear

POR-22481

Open in Web View Automation 

Skip in-product notification dispatch when the platform reports a company
has no client users for message channel creation, and avoid fan-out when
company task notifications have zero recipients.

Co-authored-by: Neil Raina <makeitraina@users.noreply.github.com>
@linear-code

linear-code Bot commented Aug 17, 2026

Copy link
Copy Markdown

POR-22481

@vercel

vercel Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tasks-app Error Error Aug 17, 2026 6:11pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants