> ## Documentation Index > Fetch the complete documentation index at: https://docs.together.ai/llms.txt > Use this file to discover all available pages before exploring further. # Remediation create > Creates a new remediation for an instance. Remediations created via the API goes directly to PENDING state. Our system may trigger automated remediations that require approval. These remediations are created with PENDING_APPROVAL state. The user must call /approve to start the actual remediation process. These operations can also be rejected by calling /reject. ## OpenAPI ````yaml POST /compute/clusters/{cluster_id}/instances/{instance_id}/remediations openapi: 3.1.0 info: title: Together APIs description: The Together REST API. See https://docs.together.ai for more details. version: 2.0.0 termsOfService: https://www.together.ai/terms-of-service contact: name: Together Support url: https://www.together.ai/contact license: name: MIT url: https://github.com/togethercomputer/openapi/blob/main/LICENSE servers: - url: https://api.together.ai/v1 security: - bearerAuth: [] paths: /compute/clusters/{cluster_id}/instances/{instance_id}/remediations: post: tags: - RemediationService description: >- Creates a new remediation for an instance. Remediations created via the API goes directly to PENDING state. Our system may trigger automated remediations that require approval. These remediations are created with PENDING_APPROVAL state. The user must call /approve to start the actual remediation process. These operations can also be rejected by calling /reject. operationId: RemediationService_CreateRemediation parameters: - name: cluster_id in: path required: true schema: type: string - name: instance_id in: path required: true schema: type: string - name: remediation_id in: query schema: description: Client-specified ID for idempotency. type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/Remediation' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/Remediation' components: schemas: Remediation: type: object required: - id - cluster_id - instance_id - mode - trigger - state properties: id: readOnly: true type: string cluster_id: readOnly: true type: string instance_id: readOnly: true type: string mode: enum: - REMEDIATION_MODE_VM_ONLY - REMEDIATION_MODE_HOST_AWARE - REMEDIATION_MODE_EVICT_WITHOUT_REPLACEMENT - REMEDIATION_MODE_REBOOT_VM type: string description: > Remediation mode specifies how the remediation should be performed. - `REMEDIATION_MODE_VM_ONLY`: Deletes the VM and provisions a new one on any available host. - `REMEDIATION_MODE_HOST_AWARE`: Cordons the host, deletes the VM, and provisions a new one on a different host. trigger: readOnly: true enum: - REMEDIATION_TRIGGER_MANUAL - REMEDIATION_TRIGGER_AUTOMATED type: string description: > RemediationTrigger specifies how the remediation was triggered. - `REMEDIATION_TRIGGER_MANUAL`: A user-initiated remediation (either via web UI or API call). - `REMEDIATION_TRIGGER_AUTOMATED`: A system-initiated remediation that requires approval. state: readOnly: true enum: - PENDING_APPROVAL - PENDING - RUNNING - SUCCEEDED - FAILED - CANCELLED - AUTO_RESOLVED type: string description: > RemediationState represents the lifecycle state of a remediation. - `PENDING_APPROVAL`: Awaiting approval before processing can begin. - `PENDING`: Approved and queued for processing. - `RUNNING`: Actively being processed. - `SUCCEEDED`: Successfully completed. - `FAILED`: Failed with an error. - `CANCELLED`: Cancelled by user or system. - `AUTO_RESOLVED`: The underlying issue was automatically resolved before processing. reason: type: string description: User-provided reason for the remediation. active_health_check_run_id: type: string description: Active health check run ID (UUID) that triggered this remediation. readOnly: true passive_health_check_event_id: type: string description: Passive health check event ID that triggered this remediation. readOnly: true requested_by: readOnly: true type: string description: Who requested the remediation. create_time: type: string description: When the remediation was created. format: date-time readOnly: true reviewed_by: type: string description: Who reviewed the remediation. readOnly: true review_time: type: string format: date-time description: When the remediation was reviewed. readOnly: true review_comment: readOnly: true type: string description: Review comment. start_time: type: string format: date-time description: When processing started. readOnly: true end_time: readOnly: true type: string description: When the remediation completed. format: date-time error_message: readOnly: true type: string description: Error message if the remediation failed. update_time: readOnly: true type: string description: When the remediation was last updated. format: date-time instance_name: readOnly: true type: string description: Display name of the targeted instance. linked_alerts: readOnly: true type: array items: $ref: '#/components/schemas/PassiveHealthCheckAlert' description: >- Passive health check alerts linked to this remediation, including resolved alerts. description: >- Remediation represents a node remediation request for an instance. An instance can have multiple remediations over time (e.g., failed attempts followed by retries). PassiveHealthCheckAlert: type: object required: - passive_health_check_alert_id - cluster_id - target_vm - alert_name - severity - annotations - started_at properties: passive_health_check_alert_id: readOnly: true type: string description: Primary key UUID for the passive health check alert. instance_id: readOnly: true type: string description: >- Resolved instance UUID. Empty until the alert is joined to an instance. cluster_id: readOnly: true type: string description: Cluster UUID the alert was raised against. target_vm: readOnly: true type: string description: VM name extracted from the Alertmanager labels. alert_name: readOnly: true type: string description: Alertmanager alert name. severity: readOnly: true enum: - PHC_SEVERITY_INFO - PHC_SEVERITY_WARNING - PHC_SEVERITY_CRITICAL type: string description: Canonical severity tier for the alert. annotations: readOnly: true type: object additionalProperties: type: string description: Alertmanager annotations as key-value strings. started_at: readOnly: true type: string description: Time when the underlying alert first fired. format: date-time resolved_at: readOnly: true type: string description: >- Time when the underlying alert resolved. Empty while the alert is firing. format: date-time node_remediation_intent_id: readOnly: true type: string description: Remediation intent UUID attached to this alert, if any. description: Passive health check alert returned by the health check API. securitySchemes: bearerAuth: type: http scheme: bearer x-bearer-format: bearer x-default: default ````