Flag Generation Issues and Improve Recovery Workflow

While building projects, there are situations where a generation produces results that do not follow instructions or unintentionally revert previously applied changes. When this happens, the recommended solution is to revert and attempt the generation again.

Currently there is no way to mark a specific generation as problematic or indicate that the output did not execute correctly. Reverting also continues to consume credits, which can make iterative correction expensive when users are trying to stabilize elements of a project.

A helpful improvement would include two capabilities. First, allow users to flag a message or generation as an issue so the system can record when outputs do not behave as expected. Second, consider adding a small credit adjustment when a generation is reverted due to an execution problem. For example, returning a small percentage of the credits used (such as 2% on the first revert) would acknowledge the failed iteration while still protecting the platform from abuse.

These changes would improve the iteration workflow and give the product team clearer visibility into where the generation process struggles to maintain project state or follow instructions. It would also make the build experience more efficient for users working through multiple refinement cycles.