> ## Documentation Index
> Fetch the complete documentation index at: https://developers.phrase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Discard ongoing LQA Assessment

> Discards the in-progress Language Quality Assessment (LQA) for the specified job, removing all recorded issues and resetting the assessment state. Use this when an assessment was started in error or needs to be restarted from scratch.

The operation is synchronous and returns 204 No Content immediately on success. Calling this endpoint when no assessment is in progress is safe.

The caller must have edit permission on the job. When the project uses auto-LQA mode, only users belonging to the same organization as the job may discard assessments.

| HTTP status | Condition                                                                              |
|-------------|----------------------------------------------------------------------------------------|
| 204         | Assessment discarded successfully, or no assessment was in progress.                   |
| 403         | Caller lacks edit permission on the job, or belongs to a different organization in     |
|             | auto-LQA mode. Verify the token has sufficient privileges and retry.                   |
| 404         | No job with the supplied UID exists or is visible to the caller. Check the UID value.  |




## OpenAPI

````yaml /openapi/phrase-tms-latest.json delete /api2/v1/lqa/assessments/{jobUid}
openapi: 3.0.0
info:
  description: |-
    Welcome to Phrase's TMS API documentation. 

     Please visit our [help center](https://support.phrase.com/hc/en-us/sections/5709662083612) for more information about the APIs. 

     If you have any questions, please contact [Support](https://support.phrase.com/hc/requests/new). 

     Please, include the `User-Agent` header with the name of your application or project. It might be a good idea to include some sort of contact information as well, so that we can get in touch if necessary. Examples of excellent `User-Agent` headers:
     > User-Agent: Example mobile app (example@phrase.com) <br/> User-Agent: ACME Inc Java 1.8 Client (http://acmeinc.com/contact)
  version: Latest
  title: Phrase TMS API
servers:
  - url: https://cloud.memsource.com/web
security:
  - ApiToken: []
  - OAuth2: []
tags:
  - name: Additional Workflow Step
  - name: Analysis
  - name: Async Request
  - name: Authentication
  - name: Automations
  - name: Bilingual File
  - name: Business Unit
  - name: Buyer
  - name: Client
  - name: Connector
  - name: Conversations
  - name: Cost Center
  - name: Custom Fields
  - name: Custom File Type
  - name: Domain
  - name: Due Date Scheme
  - name: Email Template
  - name: File
  - name: Glossary
  - name: Import settings
  - name: Job
  - name: Language AI
  - name: Language Assets
  - name: Language Quality Assessment
  - name: Machine Translation
  - name: Machine Translation Settings
  - name: Mapping
  - name: Net Rate Scheme
  - name: Notifications
  - name: Price List
  - name: Project
  - name: Project Template
  - name: Provider
  - name: Quality Assurance
  - name: Quality Profile
  - name: Quote
  - name: Reference File
  - name: SCIM
  - name: Segment
  - name: Segmentation Rules
  - name: Service
  - name: Spell Check
  - name: SubDomain
  - name: Supported Languages
  - name: Term Base
  - name: Translation
  - name: Translation Memory
  - name: User
  - name: Vendor
  - name: Webhook
  - name: Workflow Step
  - name: Workflow changes
  - name: XML Assistant
paths:
  /api2/v1/lqa/assessments/{jobUid}:
    delete:
      tags:
        - Language Quality Assessment
      summary: Discard ongoing LQA Assessment
      description: >
        Discards the in-progress Language Quality Assessment (LQA) for the
        specified job, removing all recorded issues and resetting the assessment
        state. Use this when an assessment was started in error or needs to be
        restarted from scratch.


        The operation is synchronous and returns 204 No Content immediately on
        success. Calling this endpoint when no assessment is in progress is
        safe.


        The caller must have edit permission on the job. When the project uses
        auto-LQA mode, only users belonging to the same organization as the job
        may discard assessments.


        | HTTP status |
        Condition                                                                             
        |

        |-------------|----------------------------------------------------------------------------------------|

        | 204         | Assessment discarded successfully, or no assessment was
        in progress.                   |

        | 403         | Caller lacks edit permission on the job, or belongs to a
        different organization in     |

        |             | auto-LQA mode. Verify the token has sufficient
        privileges and retry.                   |

        | 404         | No job with the supplied UID exists or is visible to the
        caller. Check the UID value.  |
      operationId: discardOngoingAssessment
      parameters:
        - name: jobUid
          in: path
          description: UID of the job whose in-progress LQA assessment should be discarded
          required: true
          schema:
            type: string
      responses:
        '204':
          description: No Content
        '400':
          description: Bad request
        '401':
          description: Not authorized
        '403':
          description: Forbidden
        '404':
          description: Not Found
        '405':
          description: Method not allowed
        '408':
          description: Timeout
        '410':
          description: Gone
        '415':
          description: Unsupported media type
        '429':
          description: Too many requests
        '500':
          description: Internal server error
        '501':
          description: Not implemented
components:
  securitySchemes:
    ApiToken:
      description: >-
        Get a token from `auth/login` [endpoint](#operation/login) and then pass
        it in the `Authorization` HTTP header in every subsequent API call. For
        more information visit our [help
        center](https://support.phrase.com/hc/en-us/articles/5709662181404-API-Authentication-TMS-#token-0-0).
      type: apiKey
      name: Authorization
      in: header
    OAuth2:
      description: >-
        A standard OAuth 2.0 authorization code flow. For more information visit
        our [help
        center](https://support.phrase.com/hc/en-us/articles/5709662181404-API-Authentication-TMS-#oauth-2-0-0-1).
      type: oauth2
      flows:
        authorizationCode:
          authorizationUrl: https://cloud.memsource.com/web/oauth/authorize
          tokenUrl: https://cloud.memsource.com/web/oauth/token
          scopes: {}

````