SuperAPI AI Directory

feishu-troubleshoot

Office & productivity

View repository

Updated 10-15 23:48

About this skill

Feishu Plugin Troubleshooting

❓ Frequently Asked Questions (FAQ)

No response when clicking card buttons

Symptom: After clicking a card button, there is no response, and then an error is prompted.

Cause: The app has not enabled the "Message Card Callback Interaction" permission.

Resolution Steps:

  1. Log in to the Feishu Open Platform:https://open.feishu.cn/app
  2. Select your app → Events & Callbacks
  3. In the callback configuration, change the subscription method to "Long Connection" and add the callback "Card Callback Interaction" (card.action.trigger)
  4. Create an app version → Submit for review → Publish

🔍 Diagnostic Command (Deep Tool)

Note: The diagnostic command is only used to troubleshoot complex/difficultpermission-related issues. Regular permission issues will automatically trigger the authorization process, and manual diagnosis is not required.

When to Use Diagnosis:

  • Still reporting errors after multiple authorizations
  • Issues that the automatic authorization process cannot resolve
  • Need to view the complete permission configuration status

How to Use:

Enter directly in a Feishu chat conversation (send as a user message):

/feishu doctor

The diagnostic command checks:

  • 📋 Diagnostic Summary(shown first):

    • Overall status (✅ Normal / ⚠️ Warning / ❌ Failed)
    • List of discovered issues and brief descriptions
  • Environment Information:

    • Plugin version
  • Account Information:

    • Credential completeness (appId, appSecret masked)
    • Account enabled status
    • API connectivity test
    • Bot information (name and openId)
  • App Identity Permissions:

    • Number of required permissions enabled for the app
    • List of missing required permissions
    • One-click application link (automatically includes missing permission parameters)
  • User Identity Permissions:

    • User authorization status statistics (✓ Valid / ⟳ Needs refresh / ✗ Expired)
    • Token auto-refresh status (whether offline_access is included)
    • Permission comparison table (app enabled vs user authorized, item-by-item comparison)
    • Application guidance and links when app permissions are missing
    • How to reauthorize when user authorization is insufficient