Quick answer: Verify the recipe's required research node is unlocked inside the craft execution itself, not just when populating the UI list.
Players craft an end-game item before researching its tech, often by hotbar or a stale menu. The gate exists only in the UI, so the actual craft path skips it.
How to fix it
1. Gate in the craft function
At the start of the craft, confirm every required research node for the recipe is unlocked. UI-only hiding is bypassable through cached or scripted craft calls.
2. Centralize the unlock check
Expose one IsRecipeAvailable function used by both the UI filter and the craft executor, so the rule cannot drift between display and enforcement.
3. Audit auto-craft and queues
Make sure queued or automated crafts re-validate the tech gate when they execute, since research could have been refunded or reset since they were queued.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every Unreal Engine error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
A crash you can name from its stack trace is a crash you can usually fix in minutes.