dify - 💡(How to fix) Fix In Dify version **1.13.3**, the **Copy** button for API keys in Workflows does not work. [1 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#35713Fetched 2026-04-30 06:45:17
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
Timeline (top)
closed ×1commented ×1labeled ×1mentioned ×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.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Go to a published Workflow.
  2. In the API Access / Service API section, find the API key.
  3. Click the Copy button next to the API key.

✔️ Expected Behavior

The API key should be copied to the clipboard.

❌ Actual Behavior

Nothing happens when clicking the Copy button.
If the key was not saved elsewhere, the only way to get it again is to regenerate a new one.

extent analysis

TL;DR

The issue can be resolved by investigating and fixing the JavaScript code responsible for handling the Copy button click event in the API Access section.

Guidance

  • Verify that the Copy button has a properly assigned click event handler in the frontend code.
  • Check the browser console for any errors when clicking the Copy button to identify potential JavaScript issues.
  • Inspect the HTML structure of the API Access section to ensure the Copy button is correctly linked to the API key element.
  • Test the Copy functionality in different browsers to determine if the issue is browser-specific.

Example

No code example can be provided without accessing the specific frontend codebase, but the investigation should focus on the JavaScript code handling the Copy button's onclick event.

Notes

The root cause of the issue is likely related to a frontend code problem, possibly with the event handler or the clipboard API interaction. Without access to the code, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by manually selecting and copying the API key until the root cause is identified and fixed, as regenerating a new key is not a viable long-term solution.

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