---
title: "Comment by Hassan Latif on \"How to skip all callbacks for all models in Rails\" | Hashnode"
description: "Approach 3 is not correct for production applications. As we know that production applications is multi threaded and handles multiple requests at a single time."
url: "https://hashnode.com/posts/how-to-skip-all-callbacks-for-all-models-in-rails/65388d84e8cbc7df1018d212/comment/667c8b746c98acbcc3d37e71"
---

[Discussion](https://hashnode.com/posts/how-to-skip-all-callbacks-for-all-models-in-rails/65388d84e8cbc7df1018d212)

Comment [How to skip all callbacks for all models in Rails](https://hashnode.com/posts/how-to-skip-all-callbacks-for-all-models-in-rails/65388d84e8cbc7df1018d212)

[Hassan Latif](https://hashnode.com/@Hassan787)

[Jun 26, 2024](https://hashnode.com/posts/how-to-skip-all-callbacks-for-all-models-in-rails/65388d84e8cbc7df1018d212/comment/667c8b746c98acbcc3d37e71)

Approach 3 is not correct for production applications. As we know that production applications is multi threaded and handles multiple requests at a single time. So If I have used this approach for a model lets say User and lets say my piece of code is running for one thread and same model is being called from another call then its validations and callbacks will be skipped for the second call as well. This approach can work for single threaded applications but this is not thread safe approach.

[Lucian Ghinda](https://hashnode.com/@lucianghinda)

[Jul 9, 2024](https://hashnode.com/posts/how-to-skip-all-callbacks-for-all-models-in-rails/65388d84e8cbc7df1018d212/comment/667c8b746c98acbcc3d37e71#reply-668d233efae1710919572c51)

Yes, I think in the case of multi-thread that approach will not work. I also added to it a big warning :) so it would not be an approach that I will reach for easily.