Run History

run history & workflow reproducibility why this matters a client asks you to recreate last tuesday's output with a small tweak which workflow was it? what model? what seed? what prompt? if you're running comfyui locally, the answer is probably "i don't know " on floyo, every generation is logged the workflow, the settings, the model, the output you can find any past run, see exactly what produced it, and rerun it with one click where to find run history open the run history & queue panel from the floyo canvas sidebar you'll see a chronological list of every generation, most recent first each entry shows the output image or video the workflow that generated it a timestamp the gpu time it consumed what's saved with every run everything the full workflow state at the moment you clicked run that includes every node and connection every setting on every node (seed, steps, cfg, denoise, sampler, scheduler) which model files were loaded (diffusion model, lora, clip, vae, controlnet) input images the output this is what makes floyo different from running comfyui locally locally, there's no automatic history you have to manually save workflow files and name them yourself on floyo, it happens without you thinking about it rerunning a past generation click any run in the history panel the workflow loads into the canvas with every setting exactly as it was click run same output want to tweak it? change a setting, run again now you have two logged runs the original and the variation both traceable team wide visibility on a team plan, run history is shared admins can see every team member's generations this is useful for quality review (check what was sent to a client) debugging (someone's output looks wrong, you can see their exact settings) knowledge sharing (someone got a great result, the whole team can see how) use run history as your audit trail if a client ever questions how something was made, you can pull up the exact run, show the settings, and regenerate it usage tracking the usage tab in team settings shows gpu consumption over time filter by date range and see per member breakdowns this helps you understand who's generating what and how much compute your team is using faq how far back does run history go? as far as your account exists runs are not automatically deleted can team members see each other's run history? admins and owners can see all team members' history regular members see their own does floyo log failed runs? yes failed runs appear in history too, so you can troubleshoot what went wrong