Why was I limited?

Why was I limited?

If an upload wouldn’t analyze or an investigation was blocked, logcat.ai shows a short reason. Here’s what each one means and what to do about it.

“This log requires a capability”

Three log types need a capability on your account: telecom captures (QXDM/modem) need telecom log analysis, automotive logs (CAN/VHAL) need automotive log analysis, and kernel crash dumps (Linux core dumps and Qualcomm device ramdumps) need kernel crash dump analysis. Without it, the file uploads and is stored (and counts against your storage allowance), but analysis stops there.

The capability is checked every time the file is used, not only when it is uploaded. So if a capability is removed from your account, searches and investigations on specialized logs you analyzed earlier stop running too, and a comparison that includes one of them is refused. An investigation refused this way does not cost you units.

To unblock: ask your enterprise administrator to enable the capability, or email sales@logcat.ai. See Plans & pricing.

Everything else (bugreports, logcat, dmesg, syslog, pcap, Perfetto traces, bundles) analyzes on every account with no capability needed, as long as your access period is open (below).

“Your access to the account expired on …”

Your account’s access period has ended. The same message appears as “Your access to the account begins on …” if the period hasn’t opened yet. Either way it gives the date, and the fix is the same: ask your enterprise administrator to extend or open it, or email sales@logcat.ai.

A closed period stops more than new uploads. Analysis of files you already hold stops too, including re-running one that was analyzed before, and those files report PLAN_RESTRICTED. So a file you’d watched progressing can start reporting restricted, and a re-upload you were told would pick up a fix is refused with this message instead. An active paid subscription overrides a closed period.

“Storage limit reached”

You’ve used your storage allowance for this period. The message shows how much you’ve used, your total, and how much the file needs. Your allowance refills on the reset date in the message. If you need more before then, email sales@logcat.ai for a larger allowance or a credit pack.

Note that deleting a file removes it from your workspace but doesn’t return its bytes to your allowance for the current period.

“Investigation limit reached”

You’ve spent your investigation-unit budget for this period. The message shows how many units you’ve used, your total, how many the blocked investigation needs, and your reset date. Options: wait for the reset, or email sales@logcat.ai for a bigger budget or a bonus credit pack (which stacks on top of your allowance).

“File too large”

Uploads are capped at 250 MB per file, on every account. If your file is larger, split it or narrow the capture window. Kernel debug images are the exception: upload them through the References library, where the 250 MB cap doesn’t apply. See Supported file types.

Still stuck?

Your billing page shows your live capabilities, storage, unit balance, and reset date in one place, so start there. If a block doesn’t match what you expect, see Troubleshooting or email support@logcat.ai.