# handleAsyncUpdate never called for ValueSource

**URL:** <https://forum.juce.com/t/handleasyncupdate-never-called-for-valuesource/45180>\
**Category:** Development\
**Created:** [March 24, 2021, 8:29am UTC](https://forum.juce.com/t/handleasyncupdate-never-called-for-valuesource/45180 "2021-03-24T08:29:17Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ed95](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ed95/32/7635_2.png) [@ed95](https://forum.juce.com/u/ed95)\
**Post date:** [April 8, 2021, 11:46am UTC](https://forum.juce.com/t/handleasyncupdate-never-called-for-valuesource/45180/7 "2021-04-08T11:46:04Z")

</div>

> [@Messages are only being handled while the editor is open](https://forum.juce.com/t/messages-are-only-being-handled-while-the-editor-is-open/45165/11):
>
> We’ve pushed some commits to the develop branch which should fix this. As predicted, the interaction between the host’s run loop and the shared message thread is a little tricky and there is some variation in how hosts implement the run loop interface so any feedback on the new changes would be appreciated.

---

_[View the full topic](https://forum.juce.com/t/handleasyncupdate-never-called-for-valuesource/45180)._
