# Bug: After resuming run at a given step, previously logged images disappear

**URL:** <https://community.wandb.ai/t/bug-after-resuming-run-at-a-given-step-previously-logged-images-disappear/9101>\
**Category:** W&B Help\
**Tags:** wandb\
**Created:** [February 28, 2025, 2:56pm UTC](https://community.wandb.ai/t/bug-after-resuming-run-at-a-given-step-previously-logged-images-disappear/9101 "2025-02-28T14:56:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hookxs](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hookxs](https://community.wandb.ai/u/hookxs)\
**Post date:** [February 28, 2025, 2:56pm UTC](https://community.wandb.ai/t/bug-after-resuming-run-at-a-given-step-previously-logged-images-disappear/9101/1 "2025-02-28T14:56:54Z")

</div>

Using the (relatively new) functionality `wandb.init(..., resume_from=f"id?_step=N)`, runs can be resumed at a given step and previously logged metrics for steps N+1, … will be overwritten. The data for steps 0-N should stay. This seems to work for scalars but does not work for images, based on my observation.  
If a run logs images and crashes at iteration \>N, the images are initially logged correctly (they can be displayed in the web interface). However, when I resume the run at step=N using the method above, all the images for steps 0-N are suddenly not available while the newly logged images for steps \>N are again ok. In the web interface, the previous images for steps 0-N are “seemingly there” - the step slider goes to 0 - but they take forever to load and effectively cannot be displayed.  
I can provide a minimal example code if interested.