> ## Documentation Index > Fetch the complete documentation index at: https://docs.cognigy.com/llms.txt > Use this file to discover all available pages before exploring further. # Get upcoming scheduled runs > Retrieve list of upcoming scheduled simulation runs with scenario name, next run time, and frequency information. ## OpenAPI ````yaml https://api-trial.cognigy.ai/testing/openapi/openapi-viewer.json get /dashboard/upcoming-scheduled-runs openapi: 3.0.0 info: title: SIMULATOR OPENAPI REST-ful-API Reference version: 2025.20.0 description: > ### Introduction This is the [OpenAPI 3.0](https://swagger.io/specification/) documentation of the [REST](https://en.wikipedia.org/wiki/Representational_state_transfer)-ful SIMULATOR OPENAPI API. ### Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/), which allows cross-domain communication from the browser. All responses have a wildcard same-origin header which makes the API completely accessible. ### Authentication SIMULATOR OPENAPI offers following forms of authentication: - Bearer Token (JWT) - API Key ### Error Handling This API uses HTTP status codes equal or above 400 to indicate errors. Error details are generated in compliance with [RFC 7807 - "Problem Details for HTTP APIs"](https://tools.ietf.org/html/rfc7807). Every error response contains a traceId, which should be provided to the SIMULATOR OPENAPI Technical Support when reporting an error. contact: name: Cognigy Technical Support url: https://www.cognigy.com email: support@cognigy.com license: name: Cognigy Proprietary License servers: - url: https://api-trial.cognigy.ai/testing description: Cognigy Service Testing API security: - bearerAuth: [] - apiKeyAuth: [] tags: - name: Simulations description: >- Simulation management operations - Create, read, update, and delete simulations externalDocs: description: SIMULATOR OPENAPI Documentation url: https://docs.cognigy.com/docs/service-testing/ paths: /dashboard/upcoming-scheduled-runs: get: tags: - Dashboard summary: Get upcoming scheduled runs description: >- Retrieve list of upcoming scheduled simulation runs with scenario name, next run time, and frequency information. operationId: getDashboardUpcomingScheduledRuns parameters: - name: projectId in: query required: true schema: type: string description: Project identifier - name: scenarioIds in: query required: false schema: type: array items: type: string style: form explode: false description: >- Filter by scenario/simulation reference IDs (comma-separated or array). If not provided, includes all scenarios. example: - sim-ref-1 - sim-ref-2 - name: limit in: query required: false schema: type: integer minimum: 1 maximum: 100 default: 20 description: Maximum number of upcoming scheduled runs to return responses: '200': description: Upcoming scheduled runs retrieved successfully content: application/json: schema: type: object properties: data: type: array description: Array of upcoming scheduled runs items: type: object properties: simulationReference: type: string description: Reference ID of the simulation/scenario example: sim-ref-123 simulationName: type: string description: Name of the scenario/simulation example: Customer Support Flow Test nextRun: type: string format: date-time description: ISO 8601 date/time of the next scheduled run example: '2024-01-20T10:00:00Z' frequency: type: string enum: - Daily - Every 3 days - Weekly - Bi-weekly - Monthly description: Frequency tag for the schedule example: Daily frequencyValue: type: string description: >- Raw frequency value from the schedule (for reference) example: 0 10 * * * batchId: type: string description: ID of the simulation associated with this schedule example: batch-id-456 batchName: type: string description: Name of the simulation example: Daily Customer Support Test status: type: string enum: - IN_PROGRESS - STOPPED - COMPLETED - FAILED description: Status of the scheduled simulation example: IN_PROGRESS required: - simulationReference - simulationName - nextRun - frequency - batchId - status required: - data '400': description: Bad Request - Invalid input parameters content: application/json: schema: type: object properties: error: type: string description: Validation error message field: type: string description: Field that failed validation code: type: string description: Validation error code traceId: type: string description: Trace ID for debugging required: - error - field '401': description: Unauthorized - Invalid or missing authentication content: application/json: schema: type: object properties: error: type: string description: Unauthorized error message code: type: string description: Unauthorized error code traceId: type: string description: Trace ID for debugging required: - error '403': description: Forbidden - Insufficient permissions content: application/json: schema: type: object properties: error: type: string description: Forbidden error message code: type: string description: Forbidden error code traceId: type: string description: Trace ID for debugging required: - error '500': description: Internal Server Error - Server error content: application/json: schema: type: object properties: error: type: string description: Error message code: type: string description: Error code traceId: type: string description: Trace ID for debugging required: - error security: - bearerAuth: [] - apiKeyAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: JWT Bearer Token for authentication apiKeyAuth: type: apiKey in: header name: X-API-Key description: API Key for authentication ````