I a getting the folloiwing error. “audit backlog limits exceeded”. Everything I have seen talks about a recorder which I don’t have. I also saw something about linux. but I haven’t touched that
Just wait a second or two I will get the crystal ball and tell you what your problem is. Damn, out of stock. Need to do it the old fashion way
thought some one may have come across this problem. 75% of my issues aren’t unique. Guess this forum is different from others
The ■■■■■■■ ■■■■
Asking the question
Before posting anything make sure that you read and follow the community standards
It’s all too easy to fall into the trap of the XY problem . If you describe your goal first, then others can understand what you’re trying to achieve.
If you turn up with a post that suggests you’ve put in no effort, you’re less likely to get quality help, and your post may even be ignored. Explain a bit of what you’ve done so far, such as:
Link to some other threads that you’ve found, and tried, and explain why they didn’t help you
Describe what you’ve tried, and what the problems were
Showing that you’ve put effort in will help demonstrate that you’re not simply looking for others to do all the work for you.
Tell us if you’re running Home Assistant using an official HassOS image, a Docker install, a venv install, and so on. Things that are often really useful to know include:
What version number of Home Assistant are you running?
How you installed it. If you’re not using a HassOS based install, remember to tell us the operating system
Any relevant code - correctly formatted
For example:
Home Assistant 2022.11.0 using the HassOS image Home Assistant 2021.12.2 in a venv following this guide on Windows 10 Home Assistant 2022.2.42 on Ubuntu 22.04 following this guide
Please remember that words like latest , current , newest and so on are not version numbers.
If something isn’t working, check the logs and see if things are being logged. The Home Assistant log is available in the UI, though information on custom components only appears in the log file on disk, or you can check them using the command line - ha core logs. Keep in mind that the UI will only show errors, and other entries may be helpful and relevant. Other sources will include:
Home Assistant log file homeassistant.log
Supervisor log
Add-on logs
For automations and scripts make sure to include the debug trace . Downloading and sharing the trace’s .json file is an efficient way to provide us with information about how your automation is designed an what is failing.
The more you tell us, the more likely it is that the problem can be identified.
Was a hint to provide more (essential) information so other users are actually able to provide you with help
This is much clearer (your response)
tom_l
February 20, 2026, 3:54am
7
If you are keeping any history to display in graphs and such then you do have a recorder.
Thanks. I dont think I was BUT. I restored a much earlier snap shot and rebuilt. The was a reason I couldn’t give. HA OS or Core version. which are now 17.1 and 2026.2.2
