- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip coder
- uip context-grounding
- uip docsai
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- create-project
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-library-object-repository
- get-object-repository
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-instances
- list-workflow-examples
- pack
- publish
- remote
- restore
- run, debug & execution
- run-file
- search-templates
- start-studio
- stop-execution
- tm
- uia
- uip tasks
- uip traces
- uip traces feedback
- Migration
- Reference & support
Syntax and options for `uip insights alert-deliveries`, which reads UiPath Insights alert delivery metadata.
uip insights alert-deliveries reads metadata about where an alert's notifications are sent. This is a read-only, by-ID-only surface — there is no list verb; look up a deliveryId from an alerts or alert-history row first.
Recipient identities are never returned, by design — not even in a redacted form. Use recipientCount to confirm a delivery has recipients configured.
Synopsis
uip insights alert-deliveries get <delivery-id>
uip insights alert-deliveries get <delivery-id>
This verb honors the global options and the standard exit codes. It does not accept -t, --tenant — it uses the tenant selected during uip login.
uip insights alert-deliveries get
Get metadata for one alert delivery by its integer ID.
Arguments
<delivery-id>(required) — the alert delivery's integer ID (thedeliveryIdfield from analertsoralert-historyrow).
Example
uip insights alert-deliveries get 7
uip insights alert-deliveries get 7
Data shape
{
"Code": "InsightsAlertDeliveryGet",
"Data": {
"id": 7,
"type": "email",
"recipientCount": 3,
"tenantMatches": true
}
}
{
"Code": "InsightsAlertDeliveryGet",
"Data": {
"id": 7,
"type": "email",
"recipientCount": 3,
"tenantMatches": true
}
}
recipientCount— the number of configured recipients.0means a broken delivery (the backend rejects saving a delivery with an empty recipient list, so a live delivery showing0indicates a defect, not an intentionally silent one).tenantMatches— whether the delivery's tenant matches your active session's tenant. This is a sanity boolean, not the tenant ID itself; afalsevalue indicates a backend defect, since the route is already scoped to your tenant.
A 404 means the delivery ID doesn't exist, or belongs to another tenant — these two causes can't be distinguished from the response.
Related
- alerts — source of the
deliveryIdon an alert definition row. - alert-history — source of the
deliveryIdon a trigger history row.