# Message bus is no longer functioning correctly

**URL:** https://meta.discourse.org/t/message-bus-is-no-longer-functioning-correctly/237209
**Category:** Support
**Created:** [August 25, 2022, 6:49pm UTC](https://meta.discourse.org/t/message-bus-is-no-longer-functioning-correctly/237209 "2022-08-25T18:49:27Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy)
#### Post date: [August 25, 2022, 6:49pm UTC](https://meta.discourse.org/t/message-bus-is-no-longer-functioning-correctly/237209/1 "2022-08-25T18:49:27Z")

</div>

I’m seeing this message show up in the logs after a recent update

> Global messages on 379645 timed out, message bus is no longer functioning correctly

Backtrace

```plaintext
message_bus-4.2.0/lib/message_bus.rb:748:in `block in new_subscriber_thread'
message_bus-4.2.0/lib/message_bus/timer_thread.rb:117:in `do_work'
message_bus-4.2.0/lib/message_bus/timer_thread.rb:95:in `block (2 levels) in queue'

```

What does it mean?

Version  
2.9.0.beta8  
([d5dc4ca0e9](https://github.com/discourse/discourse/commits/d5dc4ca0e9d370354a26d649a0dd003ab21bdeac))

---

<div class="post-metadata">

### Author: ![AhmedLoud](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ahmedloud/32/576547_2.png) [@AhmedLoud](https://meta.discourse.org/u/AhmedLoud)
#### Post date: [June 10, 2025, 2:57pm UTC](https://meta.discourse.org/t/message-bus-is-no-longer-functioning-correctly/237209/2 "2025-06-10T14:57:34Z")

</div>

I am having same warning. With a big global\_id

```plaintext
Global messages on 3244473 timed out, message bus is no longer functioning correctly

```

I am using

```plaintext
gem 'message_bus', '~> 4.4.1'

```

I also recently had issues with the long polling with streaming that’s when I noticed this warning.

Is it normal to have global message id this big ? It never resets ?

---

<div class="post-metadata">

### Author: ![AhmedLoud](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ahmedloud/32/576547_2.png) [@AhmedLoud](https://meta.discourse.org/u/AhmedLoud)
#### Post date: [April 10, 2026, 6:10pm UTC](https://meta.discourse.org/t/message-bus-is-no-longer-functioning-correctly/237209/3 "2026-04-10T18:10:44Z")

</div>

PR opened [fix: subscriber thread never self heals after half open tcp connection by Mubramaj · Pull Request #388 · discourse/message\_bus · GitHub](https://github.com/discourse/message_bus/pull/388)

---

<div class="post-metadata">

### Author: ![AhmedLoud](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ahmedloud/32/576547_2.png) [@AhmedLoud](https://meta.discourse.org/u/AhmedLoud)
#### Post date: [September 7, 2026, 3:32pm UTC](https://meta.discourse.org/t/message-bus-is-no-longer-functioning-correctly/237209/4 "2026-09-07T15:32:28Z")

</div>

Issue has been addressed and merged on version 5.0.0 of message bus:

> <https://github.com/discourse/message_bus/pull/389>
>
> follow up on https://github.com/discourse/message\_bus/pull/388 
> 
> Before openin…g this PR I first tested it on my production setup that was experiencing the "Global messages" timeout issues to make sure it fixes it without any side effect. 
> 
> Happened this morning and self healed correctly:
> 
> First warning message at 7:17 am
> 
> \`Global messages on 1 timed out, message bus is no longer functioning correctly\`
> 
> Followed by another warning
> 
> \`stream closed in another thread subscribe failed, reconnecting in 1 second.\` (7:17 am as well ) 
> 
> 
> It self healed correctly didn't have to restart the rails app . 
> 
> Closes #387

> **[message\_bus | RubyGems.org | your community gem host](https://rubygems.org/gems/message_bus/versions/5.0.0)**