# Thread unsafe lazy initialization in PostActionType

**URL:** <https://meta.discourse.org/t/thread-unsafe-lazy-initialization-in-postactiontype/225447>\
**Category:** Bug\
**Created:** [April 27, 2022, 3:28pm UTC](https://meta.discourse.org/t/thread-unsafe-lazy-initialization-in-postactiontype/225447 "2022-04-27T15:28:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [April 28, 2022, 2:50am UTC](https://meta.discourse.org/t/thread-unsafe-lazy-initialization-in-postactiontype/225447/2 "2022-04-28T02:50:15Z")

</div>

Does a simple call to `PostActionType.flag_settings` in an initializer resolve the issue? (eg: just insert here: [discourse/config/initializers/000-mini\_sql.rb at 3e0cb8ea47ea27cb3b564ac10656884739e4d78c · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/3e0cb8ea47ea27cb3b564ac10656884739e4d78c/config/initializers/000-mini_sql.rb#L4-L4) temporarily)

I guess we could synchronize this block as well. Are there any other big red flags truffle is raising?

---

_[View the full topic](https://meta.discourse.org/t/thread-unsafe-lazy-initialization-in-postactiontype/225447)._