# summary

Retrieve profiling request execution records — see which requests are queued, completed, rejected, or canceled across the org.

# description

Profiling requests are the execution records of the KYCD journey — each one tracks who submitted profiling, against which definition, and the outcome. This command retrieves those records and displays them as a six-column table: request name, status, target object, parent definition name, submitted by (user), and created date.

The command is read-only. For cancelling queued requests, use `profile request cancel`. For deleting terminal requests, use `profile request delete`.

LIFECYCLE CONTEXT: Profiling requests are created when `sf cuneiform profile` runs. Each request starts as Queued and ends in one of three terminal states: Completed (summary created and executing independently), Rejected (validation failed or capacity exceeded), or Canceled (user stopped it before processing). There are exactly 4 request statuses.

WHEN TO USE:

- After submitting profiling — "Did my requests complete? Are they still queued?"
- To triage rejections — filter by Rejected status to isolate problematic requests
- For multi-user coordination — the submitted-by column shows who triggered each request
- To check queue depth — see how many requests are waiting to be processed

RELATED COMMANDS:

- `sf cuneiform profile` — creates the requests this command lists
- `sf cuneiform profile request cancel` — cancel queued requests that should not be processed
- `sf cuneiform profile request delete` — permanently remove processed requests
- `sf cuneiform definition get` — check profiling results at the definition level

NATURAL LANGUAGE → FLAG MAPPING:
"show me all requests" → (no flags, lists all)
"what's still queued?" → --status Queued
"were any rejected?" → --status Rejected
"show canceled requests" → --status Canceled
"show more results" → --limit 100

COMMAND SEQUENCE:
`profile` → **`profile request list`** → `profile request cancel` or `summary stop` (when intervention is needed)

# flags.target-org.summary

Retrieve profiling requests from this Salesforce org. Specify the org alias or username when you have multiple authenticated orgs.

# flags.status.summary

Filter by request lifecycle status: Queued (waiting to be processed), Completed (summary created and executing), Rejected (validation failed or capacity exceeded), or Canceled (stopped before processing). There are exactly 4 valid values. Use --status Rejected for triage or --status Queued to check queue depth.

# flags.limit.summary

Control how many requests are displayed per page (default: 25, max: 200). Increase for large profiling runs where 25 results may not show the full picture.

# examples

- List all profiling requests — monitor progress after submitting profiling:

  <%= config.bin %> <%= command.id %> --target-org myOrg

- Triage rejected requests — isolate requests that need attention:

  <%= config.bin %> <%= command.id %> --target-org myOrg --status Rejected

- Check queue depth — see how many requests are waiting for processing:

  <%= config.bin %> <%= command.id %> --target-org myOrg --status Queued

- Confirm completed requests — verify which requests produced summaries:

  <%= config.bin %> <%= command.id %> --target-org myOrg --status Completed

- View more results in a large profiling run:

  <%= config.bin %> <%= command.id %> --target-org myOrg --limit 100

- Produce machine-readable output for scripting or dashboards:

  <%= config.bin %> <%= command.id %> --target-org myOrg --json

# errors.noTargetOrg

Could not determine target org username.

# errors.queryFailed

Failed to list profiling requests: %s

# output.title

Profiling Requests

# output.noRequests

No profiling requests found.