# Problem with EarlyStoppingCallback

**URL:** <https://discuss.huggingface.co/t/problem-with-earlystoppingcallback/3390>\
**Category:** 🤗Transformers\
**Created:** [January 26, 2021, 11:42am UTC](https://discuss.huggingface.co/t/problem-with-earlystoppingcallback/3390 "2021-01-26T11:42:49Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![alvations](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/alvations/32/97_2.png) [@alvations](https://discuss.huggingface.co/u/alvations)\
**Post date:** [November 16, 2022, 11:06am UTC](https://discuss.huggingface.co/t/problem-with-earlystoppingcallback/3390/12 "2022-11-16T11:06:47Z")

</div>

Was looking at EarlyStoppingCallbacks, I’ve found some quirks that might be a feature/bug where the patience kick in only after the first `save_state` is met, as documented on [[Maybe Bug] When using EarlyStopping Callbacks with Seq2SeqTraininer, training didn't stop](https://discuss.huggingface.co/t/maybe-bug-when-using-earlystopping-callbacks-with-seq2seqtraininer-training-didnt-stop/25883)

Posting the comment here, just in case anyone else found this post and had the found similar quirks when using early stopping.

---

_[View the full topic](https://discuss.huggingface.co/t/problem-with-earlystoppingcallback/3390)._