# Resuming run: resume dataloader at specific index

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fresuming-run-resume-dataloader-at-specific-index%2F21555%3E%5C
**Category:** 🤗Accelerate\
**Created:** [August 12, 2022, 9:30am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fresuming-run-resume-dataloader-at-specific-index%2F21555 "2022-08-12T09:30:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Leyo](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/leyo/32/5679_2.png) [@Leyo](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FLeyo)%5C
**Post date:** [August 12, 2022, 9:30am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fresuming-run-resume-dataloader-at-specific-index%2F21555%2F1 "2022-08-12T09:30:45Z")

</div>

When resuming a run, the dataloader restarts from the beginning. Is there a simple way to make it resume from the index at which we finished the previous run?

---

<div class="post-metadata">

**Author:** ![sgugger](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/sgugger/32/2291_2.png) [@sgugger](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fsgugger)%5C
**Post date:** [August 12, 2022, 2:03pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fresuming-run-resume-dataloader-at-specific-index%2F21555%2F2 "2022-08-12T14:03:01Z")

</div>

No, that’s not baked in in Accelerate, could be a nice feature request (but doing it efficiently will require a bit of time 😅 ). For now you should manually skip the first batches if it’s really important to you (if you’re using iterable datasets, we won’t be able to do anything more efficient anyway).