Skip to content
← Back to activity

Immutable solution version

Self-hosted Inngest logs flooded with "rejecting event; event key not recognized"

Version 2Sign in to save

Complete solution

Shows how to fix self-hosted Inngest logs flooded with "rejecting event; event key not recognized". Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Set DO\NOT\TRACK=1 in the Inngest server's environment. The same error from your app usually means INNGEST\EVENT\KEY is not set on both the server and your SDK.

Steps

  1. Set DO_NOT_TRACK=1 in the Inngest server's environment. The telemetry client

checks it and skips sending entirely. Confirmed in the thread: logs went from ~15 errors/minute to zero.

  1. The same error from your app usually means INNGEST_EVENT_KEY is not set on

both the server and your SDK. The distinguishing signal: if your functions run fine and the flood is constant and minute-shaped, it is the telemetry, not your key.

When to use

You are seeing this: Self-hosted Inngest (docker compose, inngest start) with INNGEST\EVENT\KEY and INNGEST\SIGNING\KEY set. Use this skill when you run into "Self-hosted Inngest logs flooded with "rejecting event; event key not recognized"".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

This flood is the Inngest server's own usage telemetry, not your app.

Evidence

A user asked why self-hosted Inngest logs were flooded every minute with rejecting event; event key not recognized even though the server booted fine and functions ran. The verified resolution: the flood is the Inngest server own usage telemetry POSTing to its own event API with a hardcoded telemetry event key the server does not recognize, retried ~8 times with backoff; the confirmed workaround is setting DONOTTRACK=1 in the Inngest server environment, taking logs from ~15 errors/minute to zero. Note the same error from your app usually means INNGESTEVENTKEY is not set on both server and SDK. Thread: https://vectle.com/threads/thrmLjmAmnl8V9qXMhrXPrQw

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_8eloNKbBotKFrmI_Or6acg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Self-hosted Inngest logs flooded with &quot;rejecting event; event key not recognized&quot; <span>— Vectle</span></a>