# I'm completely stalled with Event listeners

**URL:** <https://community.thunkable.com/t/im-completely-stalled-with-event-listeners/880714>\
**Category:** Questions about Thunkable X\
**Created:** [October 7, 2020, 7:47am UTC](https://community.thunkable.com/t/im-completely-stalled-with-event-listeners/880714 "2020-10-07T07:47:12Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![eddie.rebehy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/eddie.rebehy/32/67993_2.png) [@eddie.rebehy](https://community.thunkable.com/u/eddie.rebehy)\
**Post date:** [November 1, 2020, 11:38pm UTC](https://community.thunkable.com/t/im-completely-stalled-with-event-listeners/880714/21 "2020-11-01T23:38:44Z")

</div>

> [@Multiple Listeners](http://community.thunkable.com/t/multiple-listeners/813149/2):
>
> I was just working throught a similar issue. A few observations and strategies for you (and those who find this thread in the future): Having multiple listeners for the Realtime DB Component on different screens results in only one of the Change Events Triggering Creating Mulitple Realtime DB Components (one for each screen) pointing to the same firebase database allows mulitple screens to update whenever data changes Mulitple asynchronous event can be confusing. So to illustrate the point, h…

Worth posting this here. Thanks again to @drted .

---

_[View the full topic](https://community.thunkable.com/t/im-completely-stalled-with-event-listeners/880714)._
