fix: number pool initialization in multi telephony setup

If there are multiple telephony configurations, the form number should be initialized from the campaigns given telephonic configuration rather than the organization default telephonic configuration.
This commit is contained in:
Abhishek Kumar 2026-05-08 14:48:53 +05:30
parent 81a363b06e
commit 6d93be3ef6
31 changed files with 1105 additions and 238 deletions

View file

@ -0,0 +1,11 @@
---
title: "List Runs with Usage"
description: "Paginated list of workflow runs across the organization with usage and cost"
openapi: "GET /api/v1/organizations/usage/runs"
---
Returns a paginated list of runs across all agents in your organization, including duration, cost, and usage details for each run.
Use `start_date` and `end_date` (ISO 8601) to scope the window, and `page` / `limit` to paginate. Pass `filters` as a JSON-encoded string to narrow results further.
To fetch the full transcript or recording for a specific run, use [Retrieve Call Details](/api-reference/calls/get-run).

File diff suppressed because one or more lines are too long

View file

@ -119,7 +119,7 @@ We provide seamless integration with Langfuse for tracing if you want to use you
Once enabled, traces will be available for every completed call in Dograh.
<Note>
For self-hosted deployments, you can also configure Langfuse via [environment variables](/developer/environment-variables#tracing-langfuse) (`ENABLE_TRACING`, `LANGFUSE_SECRET_KEY`, `LANGFUSE_PUBLIC_KEY`, `LANGFUSE_HOST`) if you prefer. The UI settings take precedence over environment variables.
For self-hosted deployments, you can also configure Langfuse via [environment variables](/developer/environment-variables#tracing-langfuse) (`LANGFUSE_SECRET_KEY`, `LANGFUSE_PUBLIC_KEY`, `LANGFUSE_HOST`) as a default for all organizations. Tracing activates automatically once credentials are available — no separate enable flag is required. Per-organization credentials set in the UI take precedence over environment variables.
</Note>
## Quick Reference

View file

@ -23,7 +23,6 @@ The relevant required variables for each mode are noted in the descriptions belo
| `ENVIRONMENT` | `local` | Runtime environment. Affects logging and behaviour. One of `local`, `production`, `test` |
| `DEPLOYMENT_MODE` | `oss` | Deployment mode. Use `oss` for self-hosted |
| `AUTH_PROVIDER` | `local` | Authentication provider. Use `local` for OSS |
| `ENABLE_TRACING` | `false` | Enable distributed tracing via [Langfuse](/configurations/tracing) |
---
@ -105,7 +104,7 @@ Dograh uses **MinIO by default**, which is bundled with the self-hosted deployme
| `LANGFUSE_PUBLIC_KEY` | `null` | Langfuse public key |
| `LANGFUSE_SECRET_KEY` | `null` | Langfuse secret key |
Set `ENABLE_TRACING=true` alongside these to activate LLM call tracing. See the [Tracing guide](/configurations/tracing) for setup instructions.
Tracing activates automatically as soon as credentials are available — either via these environment variables (applied to all organizations) or per-organization in the UI under **Platform Settings**. If neither is set, spans are dropped silently. See the [Tracing guide](/configurations/tracing) for setup instructions.
---

View file

@ -203,6 +203,7 @@
"api-reference/calls",
"api-reference/calls/trigger",
"api-reference/calls/get-run",
"api-reference/calls/list-runs",
"api-reference/calls/download",
"api-reference/calls/inbound"
]