---
schema_version: "1"
id: 119fc177f0795e7aeebbfbb29ea57a169eee242dbb1004409a5ae80e7367635b
title: "Error: Deployment of the work items into the next stage failed"
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_troubleshooting_special_characters_component_names.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_troubleshooting_special_characters_component_names.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3deec23ed8e34a416ae88eaa89531dbeb11e96df5a40851d975da8694f86af13
description: This error occurs when deploying or promoting metadata components with unsupported special characters to a pipeline stage. The error text displays the component name and indicates that it wasn’t able to find the component in the zipped directory. To fix this error, replace the non-supported special characters with their URL-encoded versions.
products:
  - Salesforce Platform
release: "264"
---
# Error: Deployment of the work items into the next stage failed

This error occurs when deploying or promoting metadata components with unsupported special characters to a pipeline stage. The error text displays the component name and indicates that it wasn’t able to find the component in the zipped directory. To fix this error, replace the non-supported special characters with their URL-encoded versions.

DevOps Center and its underlying technologies, such as Metadata API and Salesforce CLI, support these special characters:

```
/\^$#+?()|[]{}!@$&:’,”
```

If you try to promote a component with an unsupported special character, the promotion fails. From the pipeline, click **View Details** to view the error from the Activity History page.

![The error dialog indicating that the deployment failed due to component not found in zipped directory.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/unsupported_spec_char_error.png)

To fix this error, first run a query to view the Submit Component record for the component name with the unsupported special character. Then substitute the unsupported character with its URL-encoded version.

In this example, the problematic component is a page layout named `Layout:Recruiters（LTAM）ver2` that uses full-width parentheses, which are not supported characters. These characters are commonly used in East Asian languages, particularly in Chinese, Japanese, and Korean (CJK) scripts.

1. In the DevOps Center org, run a SOQL query to identify the Submit Component record associated with the component with the unsupported special character.
    
    ```sql
    SELECT id, sf_devops__Source_Component__c, sf_devops__File_Path__c, 
    sf_devops__Change_Submission__r.sf_devops__Work_Item__r.Name FROM sf_devops__Submit_Component__c 
    WHERE sf_devops__Source_Component__c = '<source-component-name>' and 
    sf_devops__Change_Submission__r.sf_devops__Work_Item__r.Name = '<work-item-name>'
    ```
    
    Substitute the name of the <source-component-name> and <work-item-name> with your specific details.
    
    In our example, the SOQL query looks like this:
    
    ```
    SELECT id, sf_devops__Source_Component__c, sf_devops__File_Path__c, 
    sf_devops__Change_Submission__r.sf_devops__Work_Item__r.Name FROM sf_devops__Submit_Component__c 
    WHERE sf_devops__Source_Component__c = 'Layout:Recruiter__c-Recruiters（LTAM）ver2' 
    AND sf_devops__Change_Submission__r.sf_devops__Work_Item__r.Name = 'WI-000129'
    ```
    
    The query returns the file path name that contains the encoded version of the special characters.
    
    ![Developer Console after the SOQL query is run.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/soql_spec_char.png)
2. Update sf\_devops\_\_Source\_Component\_\_c to replace the special characters with its encoded version.
    
    In the sf\_devops\_\_File\_Path\_\_c field, copy the component name with the encoded special character (1), replace the non-encoded name in the sf\_devops\_\_Source\_Component\_\_c field (2). If using Developer Console as your query editor, you can double-click the fields when copying and pasting.
    
    ![Highlights the component name with encoded special characters in the File Path field, so you can replace the non-encoded special characters in the Source Component field.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/spec_char_paste.png)
3. Repeat to fix any other affected source components.
4. Save the changes.
5. Back in DevOps Center, try the promotion again.