langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 20:45:26 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Llama3.1 serial models in Azure AI Studio don't work #7725

New Issue
Closed
opened 2026-02-21 18:22:03 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:22:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @acelyc111 on GitHub (Jan 14, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.15.1

Cloud or Self Hosted

Cloud

Steps to reproduce

  1. Add a Llama3.1 model in Azure AI Studio
  2. Create a simple chatflow using the model
  3. Run the chatflow with any inputs
  4. Exception throws like:
    image

✔️ Expected Behavior

Work well.

❌ Actual Behavior

Exception throws.

Originally created by @acelyc111 on GitHub (Jan 14, 2025). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.15.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce 1. Add a Llama3.1 model in Azure AI Studio 2. Create a simple chatflow using the model 3. Run the chatflow with any inputs 4. Exception throws like: ![image](https://github.com/user-attachments/assets/91afde21-4a50-4f10-8735-e0c8bf09f13e) ### ✔️ Expected Behavior Work well. ### ❌ Actual Behavior Exception throws.
yindo added the 🐞 bugcloud labels 2026-02-21 18:22:03 -05:00
yindo closed this issue 2026-02-21 18:22:03 -05:00
yindo commented 2026-02-21 18:22:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 14, 2025):

Hello @acelyc111! I'm here to help you with any bugs, questions, or contributions you have for Dify. I can help solve bugs, answer questions, and guide you to become a contributor. Let's work together to resolve your issue.

The issue you're encountering with Llama3.1 models in Azure AI Studio might be related to validation errors in the Dify workflow editor. Common causes of such errors include:

  1. Variable Not Found Error: Ensure that all system prompts or variables are correctly set in the context.
  2. Invalid Context Structure Error: Verify that the context data structure is a string, as other types like array[object] are not supported.
  3. Invalid Variable Type Error: Check that the system prompt type is in the standard Prompt text format or Jinja syntax format.
  4. Model Not Exist Error: Make sure a model is selected for the LLM node.
  5. LLM Authorization Required Error: Ensure the model has a configured API Key.
  6. No Prompt Found Error: Confirm that the LLM node's prompt is not empty.
  7. Token Limit Exceeded Error: Ensure the input text does not exceed the token limits of the LLM node.
  8. Missing Key Parameters Error: Verify that all key parameters required by the LLM node are present.

Review these potential issues and adjust your configuration accordingly to resolve the exception [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Jan 14, 2025): <!-- Greeting --> Hello @acelyc111! I'm here to help you with any bugs, questions, or contributions you have for Dify. I can help solve bugs, answer questions, and guide you to become a contributor. Let's work together to resolve your issue. <!-- Answer --> The issue you're encountering with Llama3.1 models in Azure AI Studio might be related to validation errors in the Dify workflow editor. Common causes of such errors include: 1. **Variable Not Found Error:** Ensure that all system prompts or variables are correctly set in the context. 2. **Invalid Context Structure Error:** Verify that the context data structure is a string, as other types like `array[object]` are not supported. 3. **Invalid Variable Type Error:** Check that the system prompt type is in the standard Prompt text format or Jinja syntax format. 4. **Model Not Exist Error:** Make sure a model is selected for the LLM node. 5. **LLM Authorization Required Error:** Ensure the model has a configured API Key. 6. **No Prompt Found Error:** Confirm that the LLM node's prompt is not empty. 7. **Token Limit Exceeded Error:** Ensure the input text does not exceed the token limits of the LLM node. 8. **Missing Key Parameters Error:** Verify that all key parameters required by the LLM node are present. Review these potential issues and adjust your configuration accordingly to resolve the exception <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/error-handling/error-type.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/llms.txt)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/1b6909c4-d6c8-4de6-8b47-c9d5af78525f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/1b6909c4-d6c8-4de6-8b47-c9d5af78525f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/1b6909c4-d6c8-4de6-8b47-c9d5af78525f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/1b6909c4-d6c8-4de6-8b47-c9d5af78525f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1b6909c4-d6c8-4de6-8b47-c9d5af78525f?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/1b6909c4-d6c8-4de6-8b47-c9d5af78525f?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label cloud 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7725
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?