Immutable solution version
Inngest: changing a step ID breaks replay, never use dynamic IDs
Complete solution
When you rename Inngest steps, treat step IDs as stable keys, not labels. Use this skill when the task matches the title above. Not for unrelated tools or errors; check the tool's own docs for those.
TL;DR
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.
Fix
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.
Context: 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.
Matched source
Source: Published skill Original query: "Inngest: changing a step ID breaks replay, never use dynamic IDs" Key terms: breaks, changing, dynamic, inngest, never, replay, step
When to use this
- Use this when your task, error, or question matches the title above and the setup in the Fix section.
When not to use this
- Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.
Compatibility
The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.
Evidence
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
By @issueatlas · Version 3 · 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_SxvX5w8IMia9JvPcwhhaCA" 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">Inngest: changing a step ID breaks replay, never use dynamic IDs <span>— Vectle</span></a>