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

wecom_group_bot, return not a valid UUID #5089

New Issue
Closed
opened 2026-02-21 18:09:20 -05:00 by yindo · 11 comments
yindo commented 2026-02-21 18:09:20 -05:00
Owner
Copy Link
Copy Source

Originally created by @yshaoliang on GitHub (Aug 17, 2024).

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.7.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Integrate wecom_group-bot, send message returns invalid UUID

✔️ Expected Behavior

{"wecom_group_bot": {"content": "This is a test msg.", "hook_key": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=27ff0100-1d2a-4293-xxxx-3b9b44477a68", "message_type": "text"}}

❌ Actual Behavior

{"wecom_group_bot": "Invalid parameter hook_key $https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=27ff0100-1d2a-4293-xxxx-3b9b44477a68, not a valid UUID"}

Originally created by @yshaoliang on GitHub (Aug 17, 2024). ### 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.7.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Integrate wecom_group-bot, send message returns invalid UUID ### ✔️ Expected Behavior {"wecom_group_bot": {"content": "This is a test msg.", "hook_key": "https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=27ff0100-1d2a-4293-xxxx-3b9b44477a68", "message_type": "text"}} ### ❌ Actual Behavior {"wecom_group_bot": "Invalid parameter hook_key $https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=27ff0100-1d2a-4293-xxxx-3b9b44477a68, not a valid UUID"}
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:09:20 -05:00
yindo closed this issue 2026-02-21 18:09:20 -05:00
yindo commented 2026-02-21 18:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 17, 2024):

@yshaoliang Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's squash those bugs together! 😄

The invalid UUID error when integrating wecom_group-bot and sending a message in Dify version 0.7.0 when self-hosted with Docker is likely due to incorrect configuration of the environment variables in the docker-compose.yml file. Specifically, ensure that the DIFY_API_BASE, DIFY_API_KEY, and DIFY_APP_TYPE environment variables are correctly set.

Here is the relevant section from the documentation:

version: '2.0'
services:
  dify-on-wechat:
    image: hanfangyuan/dify-on-wechat
    container_name: dify-on-wechat
    security_opt:
      - seccomp:unconfined
    environment:
      DIFY_API_BASE: 'https://api.dify.ai/v1'
      DIFY_API_KEY: 'app-xx'
      DIFY_APP_TYPE: 'chatbot'
      MODEL: 'dify'
      SINGLE_CHAT_PREFIX: '[""]'
      SINGLE_CHAT_REPLY_PREFIX: '""'
      GROUP_CHAT_PREFIX: '["@bot"]'
      GROUP_NAME_WHITE_LIST: '["ALL_GROUP"]'

Ensure that the DIFY_API_KEY is a valid key and the DIFY_API_BASE is correctly set to your API server address [1].

Additionally, the hook_key parameter in the wecom_group_bot integration must be a valid UUID. The error message indicates that the provided hook_key is not recognized as a valid UUID. Here is a code snippet that shows the validation:

if not is_valid_uuid(hook_key):
    return self.create_text_message(
        f'Invalid parameter hook_key ${hook_key}, not a valid UUID')

Make sure that the hook_key you are using is a valid UUID [2][3].

Dify also has a specific error handling mechanism for parsing UUIDs in the WorkflowAppService class. The _safe_parse_uuid method is used to safely parse a string into a UUID. If the string is shorter than 32 characters or cannot be parsed into a valid UUID, the method returns None:

@staticmethod
def _safe_parse_uuid(value: str):
    # fast check
    if len(value) < 32:
        return None

    try:
        return uuid.UUID(value)
    except ValueError:
        return None

This method provides a detailed check to determine if a UUID is valid and logs the reason why a UUID might be considered invalid (either due to length or parsing error) [4].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 17, 2024): <!-- Greeting --> @yshaoliang Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's squash those bugs together! 😄 <!-- Answer --> The invalid UUID error when integrating `wecom_group-bot` and sending a message in Dify version 0.7.0 when self-hosted with Docker is likely due to incorrect configuration of the environment variables in the `docker-compose.yml` file. Specifically, ensure that the `DIFY_API_BASE`, `DIFY_API_KEY`, and `DIFY_APP_TYPE` environment variables are correctly set. Here is the relevant section from the documentation: ```yaml version: '2.0' services: dify-on-wechat: image: hanfangyuan/dify-on-wechat container_name: dify-on-wechat security_opt: - seccomp:unconfined environment: DIFY_API_BASE: 'https://api.dify.ai/v1' DIFY_API_KEY: 'app-xx' DIFY_APP_TYPE: 'chatbot' MODEL: 'dify' SINGLE_CHAT_PREFIX: '[""]' SINGLE_CHAT_REPLY_PREFIX: '""' GROUP_CHAT_PREFIX: '["@bot"]' GROUP_NAME_WHITE_LIST: '["ALL_GROUP"]' ``` Ensure that the `DIFY_API_KEY` is a valid key and the `DIFY_API_BASE` is correctly set to your API server address <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/use-cases/dify-on-wechat.md)</sup>. Additionally, the `hook_key` parameter in the `wecom_group_bot` integration must be a valid UUID. The error message indicates that the provided `hook_key` is not recognized as a valid UUID. Here is a code snippet that shows the validation: ```python if not is_valid_uuid(hook_key): return self.create_text_message( f'Invalid parameter hook_key ${hook_key}, not a valid UUID') ``` Make sure that the `hook_key` you are using is a valid UUID <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/wecom/tools/wecom_group_bot.py)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/wecom/tools/wecom_group_bot.yaml)</sup>. Dify also has a specific error handling mechanism for parsing UUIDs in the `WorkflowAppService` class. The `_safe_parse_uuid` method is used to safely parse a string into a UUID. If the string is shorter than 32 characters or cannot be parsed into a valid UUID, the method returns `None`: ```python @staticmethod def _safe_parse_uuid(value: str): # fast check if len(value) < 32: return None try: return uuid.UUID(value) except ValueError: return None ``` This method provides a detailed check to determine if a UUID is valid and logs the reason why a UUID might be considered invalid (either due to length or parsing error) <sup>[[4]](https://github.com/langgenius/dify/blob/main/api/services/workflow_app_service.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:09:20 -05:00
Author
Owner
Copy Link
Copy Source

@yshaoliang commented on GitHub (Aug 17, 2024):

@yshaoliang Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's squash those bugs together! 😄

The invalid UUID error when integrating wecom_group-bot and sending a message in Dify version 0.7.0 when self-hosted with Docker is likely due to incorrect configuration of the environment variables in the docker-compose.yml file. Specifically, ensure that the DIFY_API_BASE, DIFY_API_KEY, and DIFY_APP_TYPE environment variables are correctly set.

Here is the relevant section from the documentation:

version: '2.0'
services:
  dify-on-wechat:
    image: hanfangyuan/dify-on-wechat
    container_name: dify-on-wechat
    security_opt:
      - seccomp:unconfined
    environment:
      DIFY_API_BASE: 'https://api.dify.ai/v1'
      DIFY_API_KEY: 'app-xx'
      DIFY_APP_TYPE: 'chatbot'
      MODEL: 'dify'
      SINGLE_CHAT_PREFIX: '[""]'
      SINGLE_CHAT_REPLY_PREFIX: '""'
      GROUP_CHAT_PREFIX: '["@bot"]'
      GROUP_NAME_WHITE_LIST: '["ALL_GROUP"]'

Ensure that the DIFY_API_KEY is a valid key and the DIFY_API_BASE is correctly set to your API server address [1].

Additionally, the hook_key parameter in the wecom_group_bot integration must be a valid UUID. The error message indicates that the provided hook_key is not recognized as a valid UUID. Here is a code snippet that shows the validation:

if not is_valid_uuid(hook_key):
    return self.create_text_message(
        f'Invalid parameter hook_key ${hook_key}, not a valid UUID')

Make sure that the hook_key you are using is a valid UUID [2][3].

Dify also has a specific error handling mechanism for parsing UUIDs in the WorkflowAppService class. The _safe_parse_uuid method is used to safely parse a string into a UUID. If the string is shorter than 32 characters or cannot be parsed into a valid UUID, the method returns None:

@staticmethod
def _safe_parse_uuid(value: str):
    # fast check
    if len(value) < 32:
        return None

    try:
        return uuid.UUID(value)
    except ValueError:
        return None

This method provides a detailed check to determine if a UUID is valid and logs the reason why a UUID might be considered invalid (either due to length or parsing error) [4].

To continue talking to Dosu, mention @dosu.

Thanks for your help!
I have configured YAML according to your instructions and ensured that DIFY_API_BASE and DIFY_API_KEY are correct:
DIFY_API_BASE: ' http://localhost/v1 '
DIFY_API_KEY: 'app-r5WC7hymNwOYuMH8plvfAbA6'

And I also ensure that this UUID is copied from the wecom group chat robot app:
https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=27ff0100-1d2a-4293-****-3b9b44477a68

Restart Docker, log in to dify again, but still return an invalid UUID

11

@yshaoliang commented on GitHub (Aug 17, 2024): > @yshaoliang Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's squash those bugs together! 😄 > > The invalid UUID error when integrating `wecom_group-bot` and sending a message in Dify version 0.7.0 when self-hosted with Docker is likely due to incorrect configuration of the environment variables in the `docker-compose.yml` file. Specifically, ensure that the `DIFY_API_BASE`, `DIFY_API_KEY`, and `DIFY_APP_TYPE` environment variables are correctly set. > > Here is the relevant section from the documentation: > > ```yaml > version: '2.0' > services: > dify-on-wechat: > image: hanfangyuan/dify-on-wechat > container_name: dify-on-wechat > security_opt: > - seccomp:unconfined > environment: > DIFY_API_BASE: 'https://api.dify.ai/v1' > DIFY_API_KEY: 'app-xx' > DIFY_APP_TYPE: 'chatbot' > MODEL: 'dify' > SINGLE_CHAT_PREFIX: '[""]' > SINGLE_CHAT_REPLY_PREFIX: '""' > GROUP_CHAT_PREFIX: '["@bot"]' > GROUP_NAME_WHITE_LIST: '["ALL_GROUP"]' > ``` > > Ensure that the `DIFY_API_KEY` is a valid key and the `DIFY_API_BASE` is correctly set to your API server address [[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/use-cases/dify-on-wechat.md). > > Additionally, the `hook_key` parameter in the `wecom_group_bot` integration must be a valid UUID. The error message indicates that the provided `hook_key` is not recognized as a valid UUID. Here is a code snippet that shows the validation: > > ```python > if not is_valid_uuid(hook_key): > return self.create_text_message( > f'Invalid parameter hook_key ${hook_key}, not a valid UUID') > ``` > > Make sure that the `hook_key` you are using is a valid UUID [[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/wecom/tools/wecom_group_bot.py)[[3]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/wecom/tools/wecom_group_bot.yaml). > > Dify also has a specific error handling mechanism for parsing UUIDs in the `WorkflowAppService` class. The `_safe_parse_uuid` method is used to safely parse a string into a UUID. If the string is shorter than 32 characters or cannot be parsed into a valid UUID, the method returns `None`: > > ```python > @staticmethod > def _safe_parse_uuid(value: str): > # fast check > if len(value) < 32: > return None > > try: > return uuid.UUID(value) > except ValueError: > return None > ``` > > This method provides a detailed check to determine if a UUID is valid and logs the reason why a UUID might be considered invalid (either due to length or parsing error) [[4]](https://github.com/langgenius/dify/blob/main/api/services/workflow_app_service.py). > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._ Thanks for your help! I have configured YAML according to your instructions and ensured that DIFY_API_BASE and DIFY_API_KEY are correct: DIFY_API_BASE: ' http://localhost/v1 ' DIFY_API_KEY: 'app-r5WC7hymNwOYuMH8plvfAbA6' And I also ensure that this UUID is copied from the wecom group chat robot app: https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=27ff0100-1d2a-4293-****-3b9b44477a68 Restart Docker, log in to dify again, but still return an invalid UUID ![11](https://github.com/user-attachments/assets/8f538927-88d7-49d0-b6d4-9eb2389d6cc3)
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 17, 2024):

It seems like the wecom_group_bot is still returning an invalid UUID error despite your configurations. Here are a few things to double-check:

  1. UUID Validation: Ensure that the hook_key you are using is a valid UUID. The error message indicates that the provided hook_key is not recognized as a valid UUID. The validation code snippet is as follows:

    if not is_valid_uuid(hook_key):
    return self.create_text_message(
        f'Invalid parameter hook_key ${hook_key}, not a valid UUID')

    Make sure the hook_key you copied from the WeCom group chat robot app is correctly formatted as a UUID.

  2. Configuration File: Verify that your config.json file in the project root directory is correctly set up. Here is an example configuration:

    {
  "dify_api_base": "https://api.dify.ai/v1",
  "dify_api_key": "app-xxx",
  "dify_app_type": "chatbot",
  "channel_type": "wx",
  "model": "dify",
  "single_chat_prefix": [""],
  "single_chat_reply_prefix": "",
  "group_chat_prefix": ["@bot"],
  "group_name_white_list": ["ALL_GROUP"]
}

    Ensure that the dify_api_key and dify_api_base match the settings from your Dify application.

If everything seems correct and the issue persists, it might be helpful to get additional assistance. @takatost, could you take a look at this issue?

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 17, 2024): <!-- Answer --> It seems like the `wecom_group_bot` is still returning an invalid UUID error despite your configurations. Here are a few things to double-check: 1. **UUID Validation**: Ensure that the `hook_key` you are using is a valid UUID. The error message indicates that the provided `hook_key` is not recognized as a valid UUID. The validation code snippet is as follows: ```python if not is_valid_uuid(hook_key): return self.create_text_message( f'Invalid parameter hook_key ${hook_key}, not a valid UUID') ``` Make sure the `hook_key` you copied from the WeCom group chat robot app is correctly formatted as a UUID. 2. **Configuration File**: Verify that your `config.json` file in the project root directory is correctly set up. Here is an example configuration: ```json { "dify_api_base": "https://api.dify.ai/v1", "dify_api_key": "app-xxx", "dify_app_type": "chatbot", "channel_type": "wx", "model": "dify", "single_chat_prefix": [""], "single_chat_reply_prefix": "", "group_chat_prefix": ["@bot"], "group_name_white_list": ["ALL_GROUP"] } ``` Ensure that the `dify_api_key` and `dify_api_base` match the settings from your Dify application. If everything seems correct and the issue persists, it might be helpful to get additional assistance. @takatost, could you take a look at this issue? <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@yshaoliang commented on GitHub (Aug 17, 2024):

@yshaoliang Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's squash those bugs together! 😄

The invalid UUID error when integrating wecom_group-bot and sending a message in Dify version 0.7.0 when self-hosted with Docker is likely due to incorrect configuration of the environment variables in the docker-compose.yml file. Specifically, ensure that the DIFY_API_BASE, DIFY_API_KEY, and DIFY_APP_TYPE environment variables are correctly set.

Here is the relevant section from the documentation:

version: '2.0'
services:
  dify-on-wechat:
    image: hanfangyuan/dify-on-wechat
    container_name: dify-on-wechat
    security_opt:
      - seccomp:unconfined
    environment:
      DIFY_API_BASE: 'https://api.dify.ai/v1'
      DIFY_API_KEY: 'app-xx'
      DIFY_APP_TYPE: 'chatbot'
      MODEL: 'dify'
      SINGLE_CHAT_PREFIX: '[""]'
      SINGLE_CHAT_REPLY_PREFIX: '""'
      GROUP_CHAT_PREFIX: '["@bot"]'
      GROUP_NAME_WHITE_LIST: '["ALL_GROUP"]'

Ensure that the DIFY_API_KEY is a valid key and the DIFY_API_BASE is correctly set to your API server address [1].

Additionally, the hook_key parameter in the wecom_group_bot integration must be a valid UUID. The error message indicates that the provided hook_key is not recognized as a valid UUID. Here is a code snippet that shows the validation:

if not is_valid_uuid(hook_key):
    return self.create_text_message(
        f'Invalid parameter hook_key ${hook_key}, not a valid UUID')

Make sure that the hook_key you are using is a valid UUID [2][3].

Dify also has a specific error handling mechanism for parsing UUIDs in the WorkflowAppService class. The _safe_parse_uuid method is used to safely parse a string into a UUID. If the string is shorter than 32 characters or cannot be parsed into a valid UUID, the method returns None:

@staticmethod
def _safe_parse_uuid(value: str):
    # fast check
    if len(value) < 32:
        return None

    try:
        return uuid.UUID(value)
    except ValueError:
        return None

This method provides a detailed check to determine if a UUID is valid and logs the reason why a UUID might be considered invalid (either due to length or parsing error) [4].

To continue talking to Dosu, mention @dosu.

It seems like the wecom_group_bot is still returning an invalid UUID error despite your configurations. Here are a few things to double-check:

  1. UUID Validation: Ensure that the hook_key you are using is a valid UUID. The error message indicates that the provided hook_key is not recognized as a valid UUID. The validation code snippet is as follows:

    if not is_valid_uuid(hook_key):
    return self.create_text_message(
        f'Invalid parameter hook_key ${hook_key}, not a valid UUID')

    Make sure the hook_key you copied from the WeCom group chat robot app is correctly formatted as a UUID.

  2. Configuration File: Verify that your config.json file in the project root directory is correctly set up. Here is an example configuration:

    {
  "dify_api_base": "https://api.dify.ai/v1",
  "dify_api_key": "app-xxx",
  "dify_app_type": "chatbot",
  "channel_type": "wx",
  "model": "dify",
  "single_chat_prefix": [""],
  "single_chat_reply_prefix": "",
  "group_chat_prefix": ["@bot"],
  "group_name_white_list": ["ALL_GROUP"]
}

    Ensure that the dify_api_key and dify_api_base match the settings from your Dify application.

If everything seems correct and the issue persists, it might be helpful to get additional assistance. @takatost, could you take a look at this issue?

To continue talking to Dosu, mention @dosu.

Thank you for your prompt reply!

The UUID is "27ff0100-1d2a-4293-****-3b9b44477a68", and its format and content are correct.
I added channel_type="wx" in the yaml file.

I restarted Docker, but the problem still persists. Have you personally tested it?

@yshaoliang commented on GitHub (Aug 17, 2024): > @yshaoliang Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's squash those bugs together! 😄 > > The invalid UUID error when integrating `wecom_group-bot` and sending a message in Dify version 0.7.0 when self-hosted with Docker is likely due to incorrect configuration of the environment variables in the `docker-compose.yml` file. Specifically, ensure that the `DIFY_API_BASE`, `DIFY_API_KEY`, and `DIFY_APP_TYPE` environment variables are correctly set. > > Here is the relevant section from the documentation: > > ```yaml > version: '2.0' > services: > dify-on-wechat: > image: hanfangyuan/dify-on-wechat > container_name: dify-on-wechat > security_opt: > - seccomp:unconfined > environment: > DIFY_API_BASE: 'https://api.dify.ai/v1' > DIFY_API_KEY: 'app-xx' > DIFY_APP_TYPE: 'chatbot' > MODEL: 'dify' > SINGLE_CHAT_PREFIX: '[""]' > SINGLE_CHAT_REPLY_PREFIX: '""' > GROUP_CHAT_PREFIX: '["@bot"]' > GROUP_NAME_WHITE_LIST: '["ALL_GROUP"]' > ``` > > Ensure that the `DIFY_API_KEY` is a valid key and the `DIFY_API_BASE` is correctly set to your API server address [[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/use-cases/dify-on-wechat.md). > > Additionally, the `hook_key` parameter in the `wecom_group_bot` integration must be a valid UUID. The error message indicates that the provided `hook_key` is not recognized as a valid UUID. Here is a code snippet that shows the validation: > > ```python > if not is_valid_uuid(hook_key): > return self.create_text_message( > f'Invalid parameter hook_key ${hook_key}, not a valid UUID') > ``` > > Make sure that the `hook_key` you are using is a valid UUID [[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/wecom/tools/wecom_group_bot.py)[[3]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/wecom/tools/wecom_group_bot.yaml). > > Dify also has a specific error handling mechanism for parsing UUIDs in the `WorkflowAppService` class. The `_safe_parse_uuid` method is used to safely parse a string into a UUID. If the string is shorter than 32 characters or cannot be parsed into a valid UUID, the method returns `None`: > > ```python > @staticmethod > def _safe_parse_uuid(value: str): > # fast check > if len(value) < 32: > return None > > try: > return uuid.UUID(value) > except ValueError: > return None > ``` > > This method provides a detailed check to determine if a UUID is valid and logs the reason why a UUID might be considered invalid (either due to length or parsing error) [[4]](https://github.com/langgenius/dify/blob/main/api/services/workflow_app_service.py). > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._ > It seems like the `wecom_group_bot` is still returning an invalid UUID error despite your configurations. Here are a few things to double-check: > > 1. **UUID Validation**: Ensure that the `hook_key` you are using is a valid UUID. The error message indicates that the provided `hook_key` is not recognized as a valid UUID. The validation code snippet is as follows: > ```python > if not is_valid_uuid(hook_key): > return self.create_text_message( > f'Invalid parameter hook_key ${hook_key}, not a valid UUID') > ``` > > > > > > > > > > > > Make sure the `hook_key` you copied from the WeCom group chat robot app is correctly formatted as a UUID. > 2. **Configuration File**: Verify that your `config.json` file in the project root directory is correctly set up. Here is an example configuration: > ```json > { > "dify_api_base": "https://api.dify.ai/v1", > "dify_api_key": "app-xxx", > "dify_app_type": "chatbot", > "channel_type": "wx", > "model": "dify", > "single_chat_prefix": [""], > "single_chat_reply_prefix": "", > "group_chat_prefix": ["@bot"], > "group_name_white_list": ["ALL_GROUP"] > } > ``` > > > > > > > > > > > > Ensure that the `dify_api_key` and `dify_api_base` match the settings from your Dify application. > > If everything seems correct and the issue persists, it might be helpful to get additional assistance. @takatost, could you take a look at this issue? > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._ Thank you for your prompt reply! The UUID is "27ff0100-1d2a-4293-****-3b9b44477a68", and its format and content are correct. I added channel_type="wx" in the yaml file. I restarted Docker, but the problem still persists. Have you personally tested it?
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@oiuv commented on GitHub (Aug 18, 2024):

I have the same error, and I'm sure my hook_key is correct.

That's strange, the test is working normally now.
Suggestion

image

@oiuv commented on GitHub (Aug 18, 2024): I have the same error, and I'm sure my hook_key is correct. ---- That's strange, the test is working normally now. ![Suggestion](https://github.com/user-attachments/assets/5d166e4c-812b-43c0-82b1-896a3696818c) ![image](https://github.com/user-attachments/assets/25b26f04-79b8-4aea-b757-b5f0ee6f9897)
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@auxpd commented on GitHub (Oct 20, 2024):

我也碰到这个问题 ，我点击发布后，强制刷新页面， 问题得到解决。看着像是缓存问题，不确定是前端还是后端

@auxpd commented on GitHub (Oct 20, 2024): 我也碰到这个问题 ，我点击发布后，强制刷新页面， 问题得到解决。看着像是缓存问题，不确定是前端还是后端
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@oiuv commented on GitHub (Oct 24, 2024):

要命了，现在问题又出现了，的确又出现这个报错

image

@oiuv commented on GitHub (Oct 24, 2024): 要命了，现在问题又出现了，的确又出现这个报错 ![image](https://github.com/user-attachments/assets/cba8faff-ac4e-45f5-90fc-e37182c4214e)
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@oiuv commented on GitHub (Oct 24, 2024):

我认为这个issue需要重新打开

@oiuv commented on GitHub (Oct 24, 2024): 我认为这个issue需要重新打开
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@qiuyeqiang commented on GitHub (Feb 25, 2025):

要命了，现在问题又出现了，的确又出现这个报错

image

你好，我这边也出现这个问题了，想请问下，后续有解决吗？

@qiuyeqiang commented on GitHub (Feb 25, 2025): > 要命了，现在问题又出现了，的确又出现这个报错 > > ![image](https://github.com/user-attachments/assets/cba8faff-ac4e-45f5-90fc-e37182c4214e) 你好，我这边也出现这个问题了，想请问下，后续有解决吗？
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@kindcao commented on GitHub (Mar 13, 2025):

v1.0.1 fixed
Image

@kindcao commented on GitHub (Mar 13, 2025): v1.0.1 fixed ![Image](https://github.com/user-attachments/assets/090102cb-649c-46b3-8d7e-0ef34cac1682)
yindo commented 2026-02-21 18:09:21 -05:00
Author
Owner
Copy Link
Copy Source

@gdxieyue commented on GitHub (Mar 24, 2025):

When I try to input "WEBHOOK KEY" for the Environment Variables, it's cause error msg.

Image

Image

@gdxieyue commented on GitHub (Mar 24, 2025): When I try to input "WEBHOOK KEY" for the Environment Variables, it's cause error msg. ![Image](https://github.com/user-attachments/assets/f38e9160-ec24-4ddf-a03d-09590dd0acdf) ![Image](https://github.com/user-attachments/assets/28316171-7ffb-491e-af43-b1dcbf2a68be)
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 🐞 bug 🤔 cant-reproduce
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#5089
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?