CavBot Error Tracking
Find the failures that
keep coming back
in real sessions
When a page breaks, the error is only part of the story.
The real signal is where it happened, how often it
repeats, and whether visitors are running into it.
Start 14-day free trial
Available on all paid plans
The same issue is repeating
on a busy page
Risk
24
Error volume
Last 24 hours
Impact path
Grouped by route
Fix first
Repeating JavaScript error on a busy page. API failures are affecting sign-up attempts. Missing page is still receiving visits. Missing asset is causing repeat load errors. Low volume, but happening on a key page. Form error is stopping profile updates.
Repeating JavaScript error on a busy page. API failures are affecting sign-up attempts. Missing page is still receiving visits. Missing asset is causing repeat load errors. Low volume, but happening on a key page. Form error is stopping profile updates.
Recent events
Live stream
Stability
Today
99.2%
crash-free sessions
Error Tracking brings the problems people run into
while using your website into one simple view.
It gathers JavaScript errors, API errors, 404s,
affected routes, and affected sessions,
then
organizes them by the pages carrying the most
trouble
Every error type in one
Shows the page, the repeats, and the sessions affected.
Live error spikes. See them while they’re still happening.
Error Intelligence is available on paid plans.
The issue matters more when it’s on your busiest page.
One clean picture of stability. See
errors, 404 views, affected routes,
and crash-free sessions in the
same place.
The messy parts are easier to
read.
Error Intelligence separates
browser errors,
API failures,
missing pages, broken files,
and stability signals, so each
problem has its own place
JavaScript errors
JavaScript errors happen when code on a page fails while the page is loading or while
someone is using it.
These errors can break buttons, forms, menus, checkout steps,
account pages, and other parts of the website people depend on. Even when the page still
looks normal, one broken script
can stop an important action from working.
How to fix
Check the error message and the file or script connected to it. Look for missing values,
broken functions, failed imports, or code that is running before the page is ready.
If the same error appears often, fix it before smaller one-time errors.
A repeated JavaScript error usually means the same
part of the page is failing for more
than one visitor.
API failure
API failures happen when a page tries to send or receive information, but the request
does not go through properly.
This can affect logins, sign-ups, checkout, forms,
account updates, search, or any part of the website that needs a response from another
system. The page may still load,
but the action the visitor tried to complete can fail.
How to fix
Check the request that failed and the response it received.
Look for server errors,
missing information, blocked requests,
or a form that is sending the wrong data.
If the failure happens during an important step like signing in, paying, or submitting a form,
treat it as a high-priority issue. Visitors may not be able to finish what they came to do.
Unhandled rejection
Unhandled rejections happen when a page starts a task, but
the task fails
before the page knows how to handle it.
This can happen during a login, payment,
form submission,
file load, or any action that depends on something finishing
in
the background. The page may not fully break, but the
visitor can still be left stuck,
waiting, or unsure if the action worked.
How to fix
Check the action that failed and what the page was waiting for. Look for a request
that never came back, a file that did not load, or a response the page was not prepared to handle.
Add a clear fallback for the failed task. If the action cannot finish, the page should show a
useful message, let the visitor
try again, or safely stop instead of leaving the step broken.
404 view
A 404 view happens when someone lands on a page that no longer exists or cannot be found.
This can happen from an old link, a deleted page, a changed URL, a typo, or a button that
points to the wrong place. Even if the rest of the website works, a missing page can stop
visitors from finding what they came for.
How to fix
Check the missing URL and where the visit came from. If the page still matters, bring it back.
If the page moved, send visitors to the new version with a redirect.
If the link is wrong, update it wherever it appears. The goal is simple: people should not keep
landing on a dead page when there is a better place to send them.
Affected route
An affected route is a page where one or more problems are showing up.
One page can have more than one issue at the same time. A form may fail,
a file may be missing, or a link may send people
to the wrong place. Looking
at the page as a whole makes it easier to understand what is really going wrong.
How to fix
Open the affected page and look at the problems listed under
it. Check what is breaking,
what keeps coming back, and
which part of the page people are trying to use.
If the same page has several issues, fix that page before chasing smaller problems elsewhere.
A busy page with
multiple problems can hurt the website faster than a page
with one small error.
Affected sessions
Affected sessions show how many visits ran into the same problem.
Some issues appear once and never show up again. Others keep happening while
people are trying to use the website. When the same problem reaches more sessions,
it becomes easier to see which errors are actually getting in the way.
How to fix
Start with the issue that reached the most sessions. Check the page, the action people were taking, and the part of the website that failed.
If the same problem keeps showing up across several visits, fix it before smaller one-time issues. A repeated problem can block more people than a small error that only appeared once.
Missing asset
A missing asset means a page tried to load a file that was not found.
That file could be an image, script, font, stylesheet, video, or another part of the page. When a file is missing, the page may still open, but something can look wrong, load incorrectly, or stop working.
How to fix
Check the missing file name and the page that tried to load it.
Make sure the file still exists, the path is spelled correctly, and the website
is pointing to the right location.
If the file was renamed, moved, or removed during an update, replace the old reference
with the correct one. This stops the page from asking for a file that is no longer there.
Network issue
A network issue means the page tried to reach something, but the request did
not finish the right way.
This can happen when a service is down, a request takes too long, or another website
blocks the connection. The page may still load, but the part that depends on that request
can fail, freeze, or show the wrong result.
How to fix
Check the request that failed and the page action that caused
it. Look for the service
it was trying to reach, how long it took,
and whether the response came back correctly.
If the issue happens during login, checkout, sign-up, or another important step, check the outside service or connection first. The page may be working, but the request behind that action may not be getting through.
Stability view
A stability view shows whether a page is working smoothly for the people using it.
It brings together the errors, missing pages, affected pages, and sessions that did
not crash. This makes it easier to understand whether a page is holding up or starting
to create problems for visitors.
How to fix
Look at the pages with the most activity and compare them with the pages showing the most problems.
A small issue on an active page can matter more than a larger issue on a page people rarely visit.
Start with the page where problems are most likely to affect real visitors, then work down from there.
A failed request, missing file, old address,
or release spike
should not read like the
same issue. Each one points somewhere
different, and the fix should be just as clear
Critical errors first
Serious problems stay at the top,
with smaller warnings kept
lower in the list.
Broken requests stay clear
Failed forms, logins, checkouts,
and account
actions stay in one
place.
Missing files get caught
A missing script, image, font, or
stylesheet can leave a page
unfinished.
Old links still get visits
A removed URL can still be opened
from bookmarks, emails,
search
results, and old buttons.
Errors after updates
When something breaks after a new
release, start with the
page, file,
or action that changed.
Review without digging
The page, the error, and the reason are shown together. No hunting around to understand what went wrong.
Stay ahead of the problems that break the
experience.
Watch for errors as they
happen, connect the tools you already
use, and keep fixed issues
out of the
way while new ones stay easy to find
Always-on error checks
Watch your website 24/7 for script errors, failed requests, missing files, and broken pages before they keep affecting visitors.
Connect your site
Use CavBot with the platform you already build
on.
No rebuild, no new workflow, no extra
mess.
Fixed issues
Resolved problems move aside, while
new
errors stay easy to find.