Source code Stability Code quality

Silent failure / fire-and-forget

Part of the Observability gaps check · fix arrives as a pull request

What it is

An async operation is started without awaiting or handling its result — a fire-and-forget call whose failure nothing observes.

Why it matters

The feature simply does not happen sometimes, and no error is recorded. Webhooks, analytics, and notification sends fail this way for weeks before someone notices the numbers are wrong.

How to fix it

Await the call, or hand it to a queue that records failures and retries them. If it genuinely must be fire-and-forget, attach a .catch() that reports the error rather than discarding it.

Run them all on your app

Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.