Troubleshooting

Most problems in CloudMonitor are one of five things. They’re listed here in the order worth checking, which is roughly how often each turns out to be the answer.

A report is empty

1. Check the Period. By a distance the most common cause. A date range with no data in it produces an empty report that is working perfectly. Try Last 30 Days before assuming anything is broken.

2. Check for a Pending cost group. If you’ve filtered to a cost group created recently, it’s marked Pending and has no spend attributed to it yet. The screen says so. See where your numbers come from.

3. Check the other filters. Provider, cost group and virtual tags all narrow every report at once, and they persist as you navigate — so a filter you set twenty minutes ago on another screen is still applied. Clearing them all is a fast way to find out.

A virtual-tag filter is worth singling out: applying one can empty a report that would otherwise have data, because tag filtering isn’t fully wired to the live path yet.

4. Consider that it might be true. “No anomalies detected” and “You’re all optimized” are real results, and CloudMonitor phrases them positively on purpose. An empty findings screen is usually good news.

5. Look for an error strip. If something genuinely failed to load, there’s a message at the top of the screen naming it. That’s an outage, not a usage question — raise it.

A screen is missing from my menu

Three possible reasons.

It’s an optional module your workspace doesn’t have. Microsoft 365, the AI spend screens and Unit Economics are all optional. Opening a saved link to one shows:

This module is switched off for your workspace. An administrator can turn it back on under Settings ▸ Workspace Settings ▸ Features.

An admin can enable it — see how to turn modules on or off.

It needs an admin role. Users & Access, Workspace Settings and Sources & Integrations are admin-only and hidden otherwise.

It’s still being built. Unit Economics shows a Coming soon card. See what isn’t available yet.

My numbers don’t match a colleague’s

Almost always one of three differences.

Cost basis. Yours might be billed where theirs is effective. It’s a personal setting, so two people genuinely can see different totals for the same period. This is the first thing to check — see effective cost vs billed cost.

Demo mode. If either of you has the Demo mode badge in the top bar, those numbers are from a fictional company.

Access. They may be a member of fewer cost groups than you, so their totals legitimately cover less. That’s the system working.

Compare filters side by side before assuming a bug: Period, provider, cost group, virtual tags, cost basis. In practice one of them differs.

I can’t see or change something

“You are not a member of any cost group.” Your membership was removed, or never added. Ask an admin or the owner of the group you need.

A screen opens read-only. Allocation rules and virtual tags are viewable by everyone and editable by admins. That’s deliberate — understanding how spend is routed is useful to all, changing it isn’t.

An option is disabled with a reason attached. CloudMonitor disables rather than hides where the reason is useful, and the reason is on the tooltip. “Every cost group needs at least one owner” and “no licensed seats available” are the two you’ll meet most.

Full detail on Roles and access.

A filter is grayed out or struck through

The report can’t honor it, and the tooltip says why. It’s not a bug — the alternative would be a filter that silently does nothing. Examples and reasoning are on filtering every report at once.

A budget shows “Requires repair”

It’s stored in a different currency from your workspace’s reporting currency, so it can’t be evaluated — and it isn’t alerting while that’s true.

CloudMonitor never converts currencies. Someone needs to re-enter the amount. See how to set currency and year.

Still stuck

Help & support at the bottom of the menu has the chat and ticket route, plus status.cloudmonitor.ai for whether CloudMonitor itself is healthy.

When you raise something, the two most useful things to include are the exact filters you had set and whether the Demo mode badge was showing. Between them they resolve most reports.