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”

Four log types need a capability on your account: telecom captures (QXDM/modem) need telecom log analysis, automotive logs (CAN/VHAL) need automotive log analysis, kernel crash dumps (Linux core dumps and Qualcomm device ramdumps) need kernel crash dump analysis, and robot recordings need robotics log 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 log-type capability needed, as long as your access period is open (below).

One capability is not about a log type. Source-grounded analysis adds source citations to findings on any log type, along with asking about that source during an investigation and requesting a candidate fix. Every account has it. Where it has been turned off nothing is refused and no analysis stops: findings arrive without source citations, and those two features are not offered.

“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.

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.

The check happens before the investigation runs, so a search you can’t afford is declined rather than run and billed afterwards. If a run you expected to work is declined, the number in the message is what it actually needs.

If your account is inside its budget and a run is still declined, the message will say why instead. Two causes do that: an access period that hasn’t opened yet or has ended, and your organization’s shared allowance being used up (below). Both are fixed by your administrator rather than by more units on your own account.

“Your organization has used its investigation units”

Some organizations buy one allowance for the whole team instead of a budget per person. Where that applies, a run is declined once the shared allowance is gone, even when your own balance still has room. The message names what the organization has used, what it bought, and the date its contract period ends.

Your own cap and the shared allowance are separate limits and a run needs both. Your cap is a ceiling on any one person rather than a reserved share of the pool, so everyone’s caps deliberately add up to more than the organization bought. That means either can stop a run first: you can be inside the shared allowance and out of your own, or the other way round, and the message tells you which.

Uploads stop too, for the same reason analysis does. Every file you upload is analyzed, so accepting a file the organization can’t pay to analyze would only defer the refusal to somewhere less useful. Everything already uploaded stays readable, and so does every result you already have.

To unblock: your organization’s administrator can raise your share out of what the contract still holds, or email sales@logcat.ai to raise the contract itself. Administrators can see what the whole organization has used on the Organization page.

When the contract period ends, new work pauses whatever allowance is left, and resumes when the period renews.

“Your organization’s data allowance for this contract period cannot take this file”

Some contracts also include a shared data allowance: how much the whole team can upload during the contract term, counted in decimal units (1 GB is 1,000,000,000 bytes) at its expanded size, so a compressed file or archive counts as the data it holds. An upload the remaining allowance cannot take in full is refused, and nothing is counted for it. Everything already uploaded stays readable.

The allowance counts data you got something from, so deleting a capture does not give its data back, but data you got nothing from is given back once the file finishes: a file that could not be processed, a file that needs a capability your organization does not have, and the files an archive skipped. If such a file is analyzed later in the same contract period, it counts again. To unblock, email sales@logcat.ai to raise the allowance, or wait for the contract period to renew. Members see the data allowance on their usage page, and owners and admins see it on the organization overview.

“Analyzing this archive costs at least …”

An archive of many small files costs more to analyze than its size alone, so its minimum price is checked against your balance before anything in it is analyzed. When that price is more than you have left, the upload is refused: the message states the price and how many files the archive holds to analyze, and nothing is drawn down. Options: wait for the reset date, or email sales@logcat.ai for a bigger budget.

“This archive holds more than 200 files to analyze”

An archive over either file limit is refused with a message saying which, and nothing in it is analyzed. Split it into smaller archives and upload them separately. The limits, and how each kind of file counts, are on Supported file types.

“This archive needs more room to unpack than …”

An archive that needs more room to unpack than one upload allows is refused before anything in it is analyzed. Split it into smaller archives and upload them separately, or email support@logcat.ai to analyze a larger one. The limit is on Supported file types.

“File too large”

The ordinary per-file cap applies on every account; formats that are large by nature (dumps, recordings, captures, traces) get a higher ceiling, decided from the file extension, so repacking one into a .zip or .tar.gz gives up the exemption. The figures and the exact list are on Supported file types. If your file is an ordinary log over the cap, split it or narrow the capture window.

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.