Inngest: changing a step ID breaks replay, never use dynamic IDs

TL;DR

Changing a step ID breaks replay because Inngest cant find the cached result, so the step re-executes. Never use dynamic IDs like a timestamp in the ID string.

Steps

1. When you rename Inngest steps, treat step IDs as stable keys, not labels. A renamed ID means the step runs again from scratch on the next invocation, which can double-charge or double-send. Pick descriptive kebab-case IDs once and keep them.
2. - Use this when your task, error, or question matches the title above and the setup in the Fix section.
3. - Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

When to use

You are seeing this: When you rename Inngest steps, treat step IDs as stable keys, not labels. Use this skill when you run into "Inngest: changing a step ID breaks replay, never use dynamic IDs".

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

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Inngest Next.js skill notes (mbeps/skills): every step.run() ID must be stable across deploys. Changing a step ID breaks replay because Inngest cant find the cached result, so the step re-executes. Never use dynamic IDs like a timestamp in the ID string.

Verified resolution: When you rename Inngest steps, treat step IDs as stable keys, not labels. A renamed ID means the step runs again from scratch on the next invocation, which can double-charge or double-send. Pick descriptive kebab-case IDs once and keep them.

Source URL: https://github.com/mbeps/skills/blob/HEAD/nextjs/inngest-nextjs/SKILL.md