dify - 💡(How to fix) Fix The API-KEY cannot be copied. There is no reaction after clicking the button. [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35155Fetched 2026-04-15 06:45:48
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
2
Author
Timeline (top)
commented ×2closed ×1labeled ×1
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.13.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Current version 1.13.2. The issue of the copy button being ineffective has occurred. After the workflow was released as an MCP service, it is impossible to copy the link. Additionally, the API-key of the knowledge base and the API-key of the workflow also have the situation where clicking the copy button does not result in any copy. Please investigate the copy logic. Thank you.

<img width="672" height="303" alt="Image" src="https://github.com/user-attachments/assets/5e7768bf-d0b3-4529-a30d-af07b6fc2d47" />

✔️ Expected Behavior

The copy should be successful.

❌ Actual Behavior

There was no response. After clicking the button, there was no reaction.

extent analysis

TL;DR

Investigate and potentially update the copy logic to resolve the issue with the copy button being ineffective in version 1.13.2.

Guidance

  • Verify that the copy button functionality is working as expected in other areas of the application to isolate the issue.
  • Check the browser console for any JavaScript errors that may be occurring when the copy button is clicked.
  • Inspect the HTML and CSS of the copy button element to ensure that it is properly configured and not being blocked by any other elements.
  • Test the copy button in different browsers to determine if the issue is browser-specific.

Example

No code snippet can be provided without more information about the copy logic implementation.

Notes

The issue may be related to a change in the MCP service release or a compatibility issue with the Docker self-hosted environment.

Recommendation

Apply workaround: Investigate and update the copy logic to resolve the issue, as the problem seems to be specific to the current implementation rather than a version-specific bug that could be fixed by an upgrade.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING