Skip to content

forcedotcom/sf-skills / plugins/builder/service-omni/skills/service-omni-channel-limits-analyze

service-omni-channel-limits-analyze

Verified

Use to report Omni-Channel Pending Service Routing usage without changing the org: query the current PendingServiceRouting count, compare it with an admin-supplied maximum or a labeled routing-model reference default, and explain which live values are unavailable through supported APIs. TRIGGER when: check Omni-Channel limits, inspect PSR limits, analyze PendingServiceRouting usage, review pending routing capacity, or report queued work usage. Do not use to change limits or scrape Salesforce Setup.

FileKindSize
SKILL.mdskill md3.8 KB
references/api-notes.mdmarkdown1.3 KB
scripts/analyze.shexecutablescript4.7 KB
scripts/tests/_bootstrap.pyscript2.6 KB
scripts/tests/test_limits_analyze_contracts.pyexecutablescript4.5 KB

references/api-notes.md

View on GitHub
# Omni-Channel limits API notes

## Supported value

`SELECT COUNT() FROM PendingServiceRouting` provides a live, point-in-time PSR row count when Omni-Channel is enabled and the running user can access the object.

## Values not exposed by a supported API

The read-only Omni-Channel Limits Setup page also displays the org's effective maximum PSR count and a rolling hourly enqueue meter. Those values are read by Salesforce's internal page controller and are not exposed as fields on `PendingServiceRouting`, Tooling objects, Metadata types, Connect resources, or the standard REST org-limits response.

The skill therefore uses these values only as labeled references:

| Routing model | Reference maximum PSRs |
|---|---:|
| Enhanced | 300,000 |
| Legacy | 200,000 |

The reference hourly maximum is 45,000. Actual org values can differ, and live hourly usage is not retrievable. An administrator can supply a known PSR maximum with `--max-psrs`, but the script still records that it was not verified through an API.

## Full-fidelity product path

Exact reporting requires a Salesforce Core product API that exposes both maximums and the rolling hourly meter, ideally through the standard REST org-limits resource. Until that contract exists, do not scrape Setup HTML or model a fictional limits sObject.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall