Timer got out of sync. Resetting

[frelev]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version): 0.42-DEV

Python release (python3 --version):

Component/platform: Core

Description of problem: In the recent versions I have been getting this a lot in log.

17-04-16 03:55:26 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-04-16 04:17:37 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-04-16 04:20:42 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-04-16 04:52:41 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-04-16 05:04:35 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-04-16 05:47:22 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-04-16 06:07:44 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

Expected: No entry in log.

Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

[n1x0id]

Same problem, just installed and almost immediately there was an error :( Raspberry Pi 3 + hass.io, last version 0.63.3

[wladwnt]

I have the same error (and as aresult slow reaction to the commands) when I run HomeAsisstant for many days. My solution currrently is to restart HA every night.

[tanis-mezzelfo]

I have the same error when I start my HA 0.64 (I had the same problem on the 0.63, too).

My "tail -f ~homeassistant/.homeassistant/home-assistant.log" output: 2018-02-26 16:38:13 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds. 2018-02-26 16:39:14 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting 2018-02-26 16:40:47 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

[psfales]

I'm seeing this error regularly (around 5 times per hour). It's happening on 0.64, but was happening on a number of earlier releases as well. I'm using a Raspberry Pi3 with HA running in a python virtualenv. In my case, it's not related to running HA for many days - I just restarted earlier today (to upgrade to 0.64) and it started happening right away

[cmsimike]

I'm curious - how is everyone running their instance of hass?

[mkyral]

My setup: python virtualenv on Debian inside LXC on my Turris 1.1 router

[jceloria]

@cmsimike In a Docker container on a Intel j1900 Dual Core 2.0GHz NUC.

[shortbloke]

@cmsimike I'm using hass on my RPi3 inside a virtualenv using Python 3.5.3 running kernel Linux HAPi3 4.9.35-v7+ #1014 SMP

[irltankman]

hass.io on Rpi2B+

[talondnb]

Hass.io on a Pi 3

On Tue, 27 Feb 2018 at 21:38, irltankman notifications@github.com wrote:

hass.io on Rpi2B+

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/7133#issuecomment-368876979, or mute the thread https://github.com/notifications/unsubscribe-auth/ADwn2x3mb1MBSZyqsOOWaVS9-BO-181jks5tZAVcgaJpZM4M-llr .

-- Regards,

Andrew Munday

[tanis-mezzelfo]

My setup is: Python virtualenv on Raspbian (stretch) on my old Raspberry Pi Model B Rev 2 ;-)

[patrik3k]

Im running 0.64.0 in Mac OSX 10.13. Get it both in plain command line hass and hass --script macos install

2018-02-28 00:06:35 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting 2018-02-28 00:06:37 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ring binary_sensor took longer than the scheduled update interval 0:00:05 2018-02-28 00:06:46 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting 2018-02-28 00:06:50 WARNING (MainThread) [homeassistant.components.sensor] Updating vera sensor took longer than the scheduled update interval 0:00:05 2018-02-28 00:06:50 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ring binary_sensor took longer than the scheduled update interval 0:00:05 2018-02-28 00:06:50 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

[Oyami-Srk]

DS216j (DSM6.1, no docker) Python3.5 with newest HA report this error after using Bluetooth LE Tracker.

[jrkoiter]

I'm also having this issue. Many times a day. Version 0.63.1 on Linux amd64.

[phdelodder]

Same issue, in most cases home-assistant becomes unresponsive and cpu spikes to 100%

Using version docker version of 0.64.3 on arch linux.

It's resulting in timer automations not working:

trigger:
     - platform: time
       minutes: '/1'
       seconds: 00

[nordicblue]

Same issue on 0.64.3 running in a virtual Ubuntu install with 1 CPU and 512MB of RAM.

I also have a trigger that fires off every 5 minutes.

trigger:
    platform: time
    minutes: '/5'
    seconds: 0

Previously I was on 0.63.3, which did not have the timer out of sync issue.

To see if this is a memory issue, I just updated the virtual server to have 1GB of RAM and 2 CPU. I'll monitor for today and will update here at end of day with results.

Let me know if there is anything else I can share about my server or install. Thanks!

[nordicblue]

Adding additional 512MB of RAM solved this issue for me. It seems that 0.64.3 just needs more resources than the previous version.

I'm not complaining, as 1GB total RAM is very acceptable and is in line with what a Pi 3 would have anyways, if I were to run HA on a Pi.

[irltankman]

How did you do that

On 7 March 2018 at 23:30, nordicblue notifications@github.com wrote:

Adding additional 512MB of RAM solved this issue for me. It seems that 0.64.3 just needs more resources than the previous version.

I'm not complaining, as 1GB total RAM is very acceptable and is in line with what a Pi 3 would have anyways, if I were to run HA on a Pi.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/7133#issuecomment-371323040, or mute the thread https://github.com/notifications/unsubscribe-auth/Aa5YZYREo7LLI2UlTNHsQnHNn4Y_Cmu7ks5tcG2KgaJpZM4M-llr .

[jrkoiter]

I'd be surprised if this issue is memory related. I have 16GB available and am seeing this issue once or twice a day.

[nordicblue]

@irltankman, I have a home server, a HP server, which runs VMWare ESXi. By using VMWare, I can run multiple servers on a single computer and one of those is a dedicated Home Assistant server running Ubuntu. So, with the use of VMWare, I can choose to assign as little RAM or as much RAM (as much as the server has) to any of the virtual servers running on my home server.

@jrkoiter, you are correct. Overnight, I received 5 new log entries of timer out of sync. Adding the memory did seem to help, as the entries are far fewer than before. But, this might be a coincidence. I reviewed the ESXi logs, for the VM CPU and RAM usage during the times that the log entries came in, and they are both low. CPU under 2% and memory under 25%.

Back to the drawing board...

[lee-costa]

@nordicblue I am running a very similar setup on a Dell server (Ubuntu VM on ESXi) and don’t have the error messages anymore. I used to see them all the time when running on a Raspberry Pi 3.

This is indeed a very strange issue.

[nordicblue]

@junior466: Just curious, how many CPU and how much RAM do you have allocated to your VM?

[dshokouhi]

I have also seen this error disappear after moving from a raspberry pi to my old plex server.

i5 2nd gen, 6gb of RAM and SSD....running ubuntu server 17.10...hass installed in a venv python 3.6.3

[lee-costa]

@nordicblue I have 1 CPU, 2GB or RAM and 25GB of hard drive space. I have also allocated 10MB for video memory. Just in case you want to try the exact setup and see where it goes.

[nordicblue]

Thanks, @junior466. It's worth a shot. Worst case, if it still happens, I'll scale it back down again.

I'll let it run for a day or so and report back.

[nordicblue]

2 CPU, 2GB of RAM, 10MB of video and 32GB of storage, it happened once in 20 hours. Unless it is coincidence, it seems to get better with more resources on the server. No guarantee without additional troubleshooting, though.

It doesn't seem that anything stops working because of these errors.

They also always seem to accompany "Unable to find service home_assistant/turn_off". Anyone else see the same in their logs?

2018-03-09 06:14:22 WARNING (MainThread) [homeassistant.core] Unable to find service home_assistant/turn_off
2018-03-09 06:25:37 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-03-09 06:37:33 WARNING (MainThread) [homeassistant.core] Unable to find service home_assistant/turn_off
2018-03-09 06:51:13 WARNING (MainThread) [homeassistant.core] Unable to find service home_assistant/turn_off
2018-03-09 07:04:05 WARNING (MainThread) [homeassistant.core] Unable to find service home_assistant/turn_off

[balloob]

Let me explain a bit what it means for the timer to get out of sync:

Home Assistant fires a time changed event every second. That is what makes the system tick. Every time when it fires an event, it will schedule itself to fire the next event. The event loop is supposed to just contain very small tasks so that we get to firing the next time event on time.

Sometimes code will not behave correctly and it does for example I/O inside the event loop. I/O is doing actual physical work and thus can add slowdowns. If the system is slowed down too much, by the time we have to fire an event, it's actually already time for the next event. (note, this error also happens if your system goes into standby or suspends via hibernation)

If you're interested, the code is actually only 15 lines: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/core.py#L1107-L1122

[nordicblue]

Thanks, @balloob , I appreciate the explanation and it makes sense. In a nutshell, something I have in my automations, for example, is getting hung and unable to complete itself in 1 second. Each automation does not spawn its own thread? Is there any way of troubleshooting what is causing the issue?

It makes sense that me adding on additional CPU and RAM helped the situation, as the system has additional resources to process everything that it needs to do. I changed the automation I had previously:

trigger:
    platform: time
    minutes: '/5'
    seconds: 0

to:

trigger:
    platform: template
    value_template: '{{ states.sensor.time.state == states.sensor.tv_off_time.state }}'

which helped. In the past 30 hours, I had 1 timer out of sync in the logs.

The other item that I continue to see is:

[homeassistant.components.media_player] Updating roku media_player took longer than the scheduled update interval 0:00:10

Which might also have something to do with the timer getting stuck/taking too long. Going to comment out all media players and see if the warnings go away completely.

[balloob]

So when a timer goes out of sync, a time trigger might actually be skipped. A state change will never fail. Always prefer state listeners over time listeners. There are just less state changes than time changes on average.

The update interval error is actually not related. It means that it takes us longer than the update interval (10 seconds in this case) to fetch the state from a Roku. If it wasn't for this guard (and warning), we would start another update process before the old one would be complete which would eventually lead up to a clogged system.

Automations don't spawn their own threads but you could have an action that calls a service that uses a thread. However, threads are run outside of the event loop and should not cause timer sync errors (unless you go 100% cpu or something).

[ebudalen]

Thank you @balloob for the explanation. Does this mean that an automation can't cause this error unless it's because the action clogs the cpu? If there is no peak at ram or cpu, is there anything we can check to try to find the culprit/culprits? Templates, specific components etc?

[balloob]

The automation itself won't cause it. That's all implemented in async with small tasks. And we can run a lot of small tasks. Don't take my word for it, run the benchmarks: hass --script benchmark will show you all the available benchmarks. We have ones for million state changed, time changed etc. On my 6yr old Mac a million state changed events takes around 8 seconds 👍

If you suspect some piece of code doing work inside the event loop, you can put the event loop in debug mode to figure it out. Note that this will slow down the whole system so don't run it all the time in this mode.

To enable debug mode, either set environment variable PYTHONASYNCIODEBUG=1 or from a custom component call hass.loop.set_debug(True).

If you run Home Assistant from the command line, setting environment variable will look like this:

 PYTHONASYNCIODEBUG=1 hass

[nordicblue]

This all great information. I will play around with debug tomorrow, to see if I can find the culprit.

Something is definitely off with my configuration, I'm pretty sure, as I am now also getting errors (randomly) for:

''Unable to find service home_assistant/turn_off''

@balloob, you are awesome for taking the time to answer everyone's questions.

[balloob]

home_assistant/turn_off -> I suspect this to be a misconfiguration on your end. The service is called homeassistant/turn_off.

[ebudalen]

Thanks again @balloob I am running HassIO, how can I set the debug mode for the loop there? Is it possible through the logger? I can access the command line through ssh, but don`t know what to write.

[balloob]

You can create a custom component. From the top of my head (so untested):

Create a file <config>/custom_components/enable_debug.py

In the file, add:

DOMAIN = 'enable_debug'

async def async_setup(hass, config):
    hass.loop.set_debug(True)
    return True

Then add to your configuration.yaml:

enable_debug:

[nordicblue]

home_assistant/turn_off -> I suspect this to be a misconfiguration on your end. The service is called homeassistant/turn_off.

That it was, It was on an automation that does not get used often. Fixed.

[ebudalen]

@balloob Thank you so much!

What I got is:

2018-03-12 17:43:41 WARNING (MainThread) [asyncio] Executing <Task finished coro=<async_enable_automation() done, defined at /usr/lib/python3.6/site-packages/homeassistant/components/automation/__init__.py:299> result=None created at /usr/lib/python3.6/site-packages/homeassistant/core.py:222> took 0.297 seconds
2018-03-12 17:43:45 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-03-12 17:43:45 ERROR (SyncWorker_5) [homeassistant.components.sensor.cert_expiry] Cannot connect to xxxxx.xxx.xxx
2018-03-12 17:43:45 WARNING (MainThread) [asyncio] Executing <Task finished coro=<Entity.async_update_ha_state() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py:186> result=None created at /usr/lib/python3.6/site-packages/homeassistant/core.py:218> took 0.478 seconds

2018-03-12 17:43:53 WARNING (MainThread) [asyncio] Executing <Task finished coro=<Group._async_state_changed_listener() done, defined at /usr/lib/python3.6/site-packages/homeassistant/components/group/__init__.py:576> result=None created at /usr/lib/python3.6/site-packages/homeassistant/core.py:222> took 0.858 seconds
2018-03-12 17:43:54 WARNING (MainThread) [asyncio] Executing <Task finished coro=<EntityPlatform._async_add_entity() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py:175> result=None created at /usr/lib/python3.6/asyncio/tasks.py:311> took 0.510 seconds
2018-03-12 17:43:55 WARNING (MainThread) [asyncio] Executing <Task finished coro=<Entity.async_update_ha_state() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py:186> result=None created at /usr/lib/python3.6/site-packages/homeassistant/core.py:218> took 0.905 seconds
2018-03-12 17:43:55 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-03-12 17:43:55 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.varmekabel_kjokken_tid_365 is taking over 10 seconds
2018-03-12 17:43:56 WARNING (MainThread) [asyncio] Executing <Task finished coro=<Entity.async_update_ha_state() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py:186> result=None created at /usr/lib/python3.6/asyncio/tasks.py:311> took 0.474 seconds

2018-03-12 17:43:57 WARNING (MainThread) [asyncio] Executing <Task finished coro=<AutomationEntity.async_trigger() done, defined at /usr/lib/python3.6/site-packages/homeassistant/components/automation/__init__.py:329> result=None created at /usr/lib/python3.6/site-packages/homeassistant/core.py:222> took 0.981 seconds
2018-03-12 17:43:57 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-03-12 17:43:58 WARNING (MainThread) [asyncio] Executing <Task finished coro=<EntityPlatform._async_add_entity() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py:175> result=None created at /usr/lib/python3.6/asyncio/tasks.py:311> took 0.509 seconds

2018-03-12 17:44:00 WARNING (MainThread) [asyncio] Executing <Task finished coro=<Entity.async_update_ha_state() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py:186> result=None created at /usr/lib/python3.6/site-packages/homeassistant/core.py:218> took 0.401 seconds
2018-03-12 17:44:00 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-03-12 17:44:00 WARNING (MainThread) [asyncio] Executing <Task finished coro=<Entity.async_update_ha_state() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py:186> result=None created at /usr/lib/python3.6/site-packages/homeassistant/core.py:218> took 0.367 seconds

2018-03-12 17:44:16 WARNING (MainThread) [asyncio] Executing <Task finished coro=<Entity.async_update_ha_state() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py:186> result=None created at /usr/lib/python3.6/site-packages/homeassistant/core.py:218> took 0.310 seconds
2018-03-12 17:44:16 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-03-12 17:44:16 WARNING (MainThread) [asyncio] Executing <Task finished coro=<Entity.async_update_ha_state() done, defined at /usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py:186> result=None created at /usr/lib/python3.6/asyncio/tasks.py:311> took 0.277 seconds

Seems like it doesn`t pass a second, but still throws an error.

Edit: Don`t know if this finds the culprit. Seems like I got a lot of the errors because I use the debug mode, got only one at startup when disabling the custom component.

[balloob]

@zepixir do you have some massive groups and triggers that listen to a lot of entities?

[ebudalen]

@balloob are you meaning size of a single group? All lights group is quite large. Yes, have some automations that have a lot of triggers. Is it better to split it up in single automations or at least fewer triggers?

[balloob]

Nah, you shouldn't have to. Our system shouldn't choke on it instead.

[ebudalen]

What I got so far is when either my custom component for hue sensors is active, or all my automations active, I get the error. Have not yet managed to get the error after 4-5 restarts if both of them isn't active. Will go back to rest-sensor for the hue sensors, and disabling some automations to try to find the culprit/culprits throughout the week. But this is not 100%, since the error not always shows even with all the automations or custom component is enabled. But will update if I find what's causing it.

[vlad36N]

Hello. I'm running HassIO on a Raspberry PI 3 Since I upgraded from 0.65.4 to 0.65.5:

Timer got out of sync. Resetting 6:16 PM core.py (ERROR) Timer got out of sync. Resetting 6:13 PM core.py (ERROR) Timer got out of sync. Resetting 6:08 PM core.py (ERROR) Timer got out of sync. Resetting 6:02 PM core.py (ERROR) Timer got out of sync. Resetting 5:57 PM core.py (ERROR) Timer got out of sync. Resetting 5:51 PM core.py (ERROR) Timer got out of sync. Resetting 5:51 PM core.py (ERROR) Timer got out of sync. Resetting 5:46 PM core.py (ERROR) Timer got out of sync. Resetting 5:40 PM core.py (ERROR) Timer got out of sync. Resetting 5:35 PM core.py (ERROR) Timer got out of sync. Resetting 5:29 PM core.py (ERROR) Timer got out of sync. Resetting 5:24 PM core.py (ERROR) Timer got out of sync. Resetting 5:18 PM core.py (ERROR) Timer got out of sync. Resetting 5:13 PM core.py (ERROR) Timer got out of sync. Resetting 5:08 PM core.py (ERROR) Timer got out of sync. Resetting 5:07 PM core.py (ERROR) Timer got out of sync. Resetting 5:02 PM core.py (ERROR) Timer got out of sync. Resetting 4:57 PM core.py (ERROR) Timer got out of sync. Resetting 4:57 PM core.py (ERROR) Timer got out of sync. Resetting 4:51 PM core.py (ERROR) Timer got out of sync. Resetting 4:46 PM core.py (ERROR) Timer got out of sync. Resetting 4:43 PM core.py (ERROR) Timer got out of sync. Resetting 4:40 PM core.py (ERROR) Timer got out of sync. Resetting 4:35 PM core.py (ERROR) Timer got out of sync. Resetting 4:29 PM core.py (ERROR) Timer got out of sync. Resetting 4:24 PM core.py (ERROR) Timer got out of sync. Resetting 4:24 PM core.py (ERROR) Timer got out of sync. Resetting 4:18 PM core.py (ERROR) Timer got out of sync. Resetting 4:13 PM core.py (ERROR) Timer got out of sync. Resetting 4:13 PM core.py (ERROR) Timer got out of sync. Resetting 4:07 PM core.py (ERROR)

[sram-narayan]

I am getting timer out of sync error when when MQTT is enabled.

Timer got out of sync. Resetting 7:25 PM core.py (ERROR) Timer got out of sync. Resetting 7:24 PM core.py (ERROR) Timer got out of sync. Resetting 7:19 PM core.py (ERROR) Timer got out of sync. Resetting 7:16 PM core.py (ERROR) Timer got out of sync. Resetting 7:14 PM core.py (ERROR) Timer got out of sync. Resetting 7:07 PM core.py (ERROR) Timer got out of sync. Resetting 7:07 PM core.py (ERROR)

[Pukington]

If it helps any I'm getting the same, currently on Home Assistant 0.65.6 on a pi3 installed via allin1. I turned on logger to check I've got HA's MQTT picking up the messages correctly and noticed Timer out of sync errors which I had none of before. When I receive a mqtt message I instantly get a timer reset, I can reproduce this at will.

2018-04-17 17:16:03 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting 2018-04-17 17:16:03 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on pihole: b'49' 2018-04-17 17:16:14 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting 2018-04-17 17:16:14 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on pihole: b'55'

[allmoney]

I have same problem. Timer got out of sync. Resetting 4:38 PM core.py (ERROR) Timer got out of sync. Resetting 4:05 PM core.py (ERROR) Timer got out of sync. Resetting 4:05 PM core.py (ERROR) Error doing job: Task was destroyed but it is pending! 4:05 PM core.py (ERROR) Timer got out of sync. Resetting 4:05 PM core.py (ERROR)

r Pi 3 B Home Assistant 0.67.1

[vswraith]

This is happening to me when I installed the dlib component.

[balloob]

Just as a note here: if you run CPU intensive processes, like dlib, and your machine is not powerful, Home Assistant's timer will also get out of sync.

[MaoX17]

+1

[sveip]

Is there a way to debug this in more detail @balloob ? I also get this error every now and the. I don't run anything special that should use much CPU. Running latest hass.io

Timer got out of sync. Resetting
1:54 PM core.py (ERROR)
Timer got out of sync. Resetting
1:33 PM core.py (ERROR)
Timer got out of sync. Resetting
1:18 PM core.py (ERROR)
Heartbeat timeout, resetting connection
1:02 PM /usr/lib/python3.6/site-packages/pychromecast/socket_client.py (WARNING)
Timer got out of sync. Resetting
12:03 PM core.py (ERROR)
Heartbeat timeout, resetting connection
11:47 AM /usr/lib/python3.6/site-packages/pychromecast/socket_client.py (WARNING)
Timer got out of sync. Resetting
11:37 AM core.py (ERROR)
Timer got out of sync. Resetting
11:36 AM core.py (ERROR)
Timer got out of sync. Resetting
11:00 AM core.py (ERROR)
Timer got out of sync. Resetting
10:37 AM core.py (ERROR)
Timer got out of sync. Resetting
10:27 AM core.py (ERROR)
Timer got out of sync. Resetting
10:22 AM core.py (ERROR)
Timer got out of sync. Resetting
10:03 AM core.py (ERROR)

[TomerFi]

@balloob Thanks for the hass.loop.set_debug(True) tip. It helped find out the cause for my Timer got out of sync. Resetting messages. Turns out I had a custom components test file I had completely forgot about and was taking more the a second to update.