Limits & Quotas
Cost Management runs on the Cloudaware platform and is subject to both Cloudaware design choices and underlying Salesforce limits, such as limits on storage, API calls, and report sizes.
Use this guide to consider common categories of limits when designing dashboards, exports, and integrations.
Data Volume and History
When planning data retention, consider the following factors:
- How many months/years of billing data you retain in Cloudaware for interactive reporting.
- Whether very long‑term or highly granular history should be archived or moved to external warehouses.
- The size of billing line‑item tables and any aggregated cost tables used for dashboards.
Large, unconstrained queries over long history can impact performance. Prefer time‑bounded and scoped queries.
Reports and Dashboards
Reports and dashboards can be subject to the following limits:
- Limits on the number of rows and summary levels per report.
- Limits on the number of components per dashboard.
- Timeouts for very complex or unfiltered reports.
Design dashboards by using summary or aggregate reports and filters rather than raw line-item views where possible.
Exports and Integrations
When exporting data or using APIs:
- Be aware of maximum export sizes (rows or file size) for scheduled reports.
- Respect API limits and governor constraints when building integrations or high‑frequency data pulls.
- Use pagination and incremental loads (for example, by date or last‑modified time) rather than full reloads where feasible.
Coordinate with your Cloudaware technical account manager to understand org-specific API and export limits.
Scheduling and Concurrency
In busy environments:
- Stagger heavy reports, exports, and ingestion jobs to avoid contention.
- Avoid scheduling large exports at the same time as major ingestion cycles or maintenance windows.
Include performance and limit monitoring in your regular Cost Management operations practices so issues can be caught and mitigated early.