API-based Variable stopped working
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
0.7.1
Cloud or Self Hosted
Cloud
Steps to reproduce
After more than a month of working without issues, I’ve recently encountered some problems.
It seems that the API-based Variable has stopped functioning as expected in the last few days. Unfortunately, I'm unable to pinpoint exactly when this issue started, though it might have occurred around the update to version 0.7 or shortly after.
I’ve verified that the endpoint is correct and accessible through Insomnia, where everything works as expected. However, according to the Cloudflare logs, it appears that Dify isn't even attempting to reach the endpoint.
The context of this bug is referenced here: #5717
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
I found a similar unsolved discussion that might be related to your issue: connection error: request error, status_code: 503 [1]. This could provide some insights or additional context for troubleshooting your problem.
To continue talking to Dosu, mention @dosu.
Same here.
Same problem after update
Same problem after update 0.7.3
API-based Variable stopped working after updating to version 0.7.3.
my system prompt:
old test:
but now like this:
I think this issue is due to this code https://github.com/langgenius/dify/blob/c5b3777d93dfbdfc0da338e1e93e909efa461548/api/core/agent/cot_agent_runner.py#L328-L338
Hello, I tried this feature on the latest version of our code. It works well. Can this issue still be reproduced?
Hello, I tried this feature on the latest version of our code. It works well. Can this issue still be reproduced?
yes, It works, but why? who fixed this bug?
Hello, I tried this feature on the latest version of our code. It works well. Can this issue still be reproduced?
I'm following up on this functionality. While it was working well in our latest code version, we've encountered a recurring timeout issue.
Details:
Previously Working: As @laipz8200 mentioned, the feature functioned correctly in recent days. Current Issue: Today, the feature stopped working again and resulted in a request timeout. Environment: We're using Hosted Dify (PRO subscription) on version 0.8.3 (signed as latest even if 0.9.1 is released on github).
Hello, I tried this feature on the latest version of our code. It works well. Can this issue still be reproduced?
Hello, I tried this feature on the latest version of our code. It works well. Can this issue still be reproduced?