langgenius
Import DSL file to create no response report
Self Checks
- [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
- [x] I have searched for existing issues search for existing issues, including closed ones.
- [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
- [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
- [x] Please do not modify this template :) and fill in all the required fields.
Dify version
1.4.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Import DSL file, create no response, console error 8871-8afeb6f8c6861834.js:1 Uncaught (in promise) TimeoutError: Request timed out: GET https://ip/console/api/version?current_version=1.4.1 at 8871-8afeb6f8c6861834.js:1:7491
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
{ "code": "unauthorized", "message": "Token has expired.", "status": 401 }imports Interface return @dosu
The "Token has expired" (401 unauthorized) error indicates that your authentication token is no longer valid. In Dify, tokens are used to authenticate API requests, and their expiration is controlled by the REFRESH_TOKEN_EXPIRE_DAYS setting in your configuration. When a token expires, any API action—including importing a DSL file—will return a 401 error until you log in again and obtain a new token. This is expected behavior for expired tokens and is not specific to the DSL import process itself.
To resolve this, log out and log back in to refresh your token. If you want to adjust how long tokens remain valid, you can change the REFRESH_TOKEN_EXPIRE_DAYS value in your Dify configuration. The token management logic, including storage and expiration, is handled in the backend using Redis and is defined in the account service codebase (source).
If you continue to see this error immediately after logging in, there may be an issue with your server's time settings or with how tokens are being issued and validated. In that case, check your Docker container's time synchronization and ensure your configuration is being loaded correctly.
There is no direct link between the DSL file content and token expiration—the error is purely about authentication. If your token is valid, the DSL import process will proceed as designed (source).
To reply, just mention my name @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
![dosubot[bot] avatar](https://avatars.githubusercontent.com/in/324583?v=4 "Published by a pub.dev verified publisher"){kind=small}
{"id": "01e3e1b2-5b8e-4c38-966f-02af8cabc2f8", "status": "failed", "app_id": null, "app_mode": null, "current_dsl_version": "0.3.0", "imported_dsl_version": "", "error": "yaml_content is required when import_mode is yaml-content"} Add DSL import error@dosu.
To import a low version DSL file into Dify version 1.4.0, you can use the "Import DSL File" feature in the Dify Studio, either by uploading a local file or providing a URL. During the import process, Dify will automatically check the version of the DSL file against the system's current DSL version (which is 0.3.0 in 1.4.0). If the imported DSL version is lower, Dify will still allow the import, but you may see a warning that version differences could affect certain features. If the version gap is significant (for example, a major version difference), the import status may be set to "pending" and you will be prompted to confirm the import despite potential incompatibilities. Minor version differences may result in a "completed with warnings" status, while micro version differences generally complete without issue. You can then review and confirm the import in the UI if prompted.
For best results and to avoid compatibility issues, it is recommended to update your DSL files to match the current version standard when possible. The official documentation also suggests exporting an updated DSL file after upgrading Dify to ensure compatibility with new features and formats. More details can be found in the Dify documentation on importing applications and DSL version compatibility.
If you encounter errors such as "yaml_content is required when import_mode is yaml-content," ensure that your import request includes the required YAML content field. If you see a "Token has expired" error, log out and log back in to refresh your authentication token.
In summary: upload or link your DSL file, review any warnings about version differences, and confirm the import if prompted. Dify will guide you through any necessary steps in the UI.
References:
To reply, just mention my name @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
After logging out and logging in again, the import of yml still reported an error, and the application creation failed {"id": "e7db9b10-7849-4074-a27e-9a36dac11c65", "status": "failed", "app_id": null, "app_made": null, "current d_dsl version": "0.3.0", "importedd_dsl version": "" "," error ":" when import_made is YAML content, YAML content is required "}. I need to correct my dify version to 1.4.1@dosu