Slack App with Hardcoded Channel ID Causing Continuous Errors - Can't Identify Which App or Access Source Code

[hardikpachory08]

Problem Description
I previously deployed a custom Slack app using the Slack CLI, but I'm now facing a critical issue with continuous error messages. The situation is complicated because:

Current Situation
❌ Cannot identify which specific Slack app is causing these errors
❌ No access to source code - I no longer have the app's directory on my system
❌ No local development environment for this app
❌ Don't remember the app name or exact configuration details
✅ I am the original creator/deployer of the problematic app
✅ App is live and deployed via Slack CLI
✅ App is actively used in multiple business channels
🚨 Continuous error spam affecting operations

Critical Requirement
I need to fix this issue WITHOUT disrupting the app's existing functionalities. The app is currently being used in important business-related channels, and any downtime or breaking changes could impact ongoing business operations. I'm looking for a solution that allows me to:

• Update only the problematic hardcoded channel ID
• Preserve all other existing workflows and features
• Maintain the app's current permissions and integrations
• Avoid any service interruption for end users

Questions:

• How can I identify which Slack app I deployed is causing these specific error messages?
• Is there a way to list all apps I've deployed using Slack CLI or through Slack's interface?
• How can I access/retrieve the source code of a deployed Slack app when I don't have the local files?
• Can I view the app's current configuration (including the problematic hardcoded channel ID) through Slack's web interface?
• Is there a way to update ONLY the hardcoded channel ID without redeploying the entire app or affecting other functionalities?
• Can I perform a targeted update/patch to fix just this specific issue while preserving everything else?
• Can I download/export the app configuration from Slack to recreate the source code safely?
• Are there any Slack CLI commands to pull down an existing app's configuration or list my deployed apps?
• How can I access the detailed error logs to get more information about which app and workflow is failing?
• What's the safest deployment strategy to fix this without breaking existing integrations?

Environment Details:

• Platform: Slack CLI
• App Type: Custom Slack app with workflows (exact details unknown)
• Deployment Status: Currently deployed and active in production
• Issue: Hardcoded channel ID pointing to deleted channel
• Developer: Me (but no longer have local setup)
• Business Impact: App is actively used in multiple important business channels

Urgency
This is affecting business operations due to continuous error notifications, and I need to identify and fix the problematic app quickly without causing any disruption to existing users or workflows. Any guidance on app identification, configuration recovery, or safe deployment practices would be greatly appreciated.

[mwbrooks]

Hi @hardikpachory08,

Sorry that you're facing this issue and the stress that it can cause when affecting business operations. 🎗️

Some quick context is that you'll need access to the source code to make code changes. The Slack Platform does not store your source code and only has access to a bundled version for runtime deployment.

Suggested first step:

In your screenshot, please click the "logs" link. This should open your browser to view the app's logs. This may give you insight into the app that is running and the URL should contain an App ID that starts with "A" and is followed by numbers (e.g. A0123). If you're able to retrieve the App ID, then Slack Support (not our open source issue tracker) may be able to help you, but unfortunately we cannot retrieve your source code. Are you able to retrieve the App ID?

How can I identify which Slack app I deployed is causing these specific error messages?

See my suggestion above.

Is there a way to list all apps I've deployed using Slack CLI or through Slack's interface?

Unfortunately, the Slack CLI requires your app's source code. You can view all of your Slack apps on https://api.slack.com/apps and knowing the App ID can help identify which app is affected.

How can I access/retrieve the source code of a deployed Slack app when I don't have the local files?

Slack doesn't store your source code. Unfortunately, the developer is responsible for storing their source code.

Can I view the app's current configuration (including the problematic hardcoded channel ID) through Slack's web interface?

You can view the app's configuration on https://api.slack.com/apps. If the Channel ID was defined in the custom function's definition then you can view it in the "app manifest" JSON. However, if the Channel ID was hard coded in source code then you may require the original source code.

Can I perform a targeted update/patch to fix just this specific issue while preserving everything else?

You can modify the app manifest in minor ways that do not change IDs that the source code depends on, but otherwise you will require the source code.

Can I download/export the app configuration from Slack to recreate the source code safely?

Similar to above, unfortunately Slack doesn't store your source code.

Are there any Slack CLI commands to pull down an existing app's configuration or list my deployed apps?

If you have the source code, then you can run Slack CLI commands inside of the project. Unfortunately, the Slack CLI cannot retrieve deployed apps without the source code. You best choice is to look on https://api.slack.com/apps for the app configuration but it doesn't store the source code.

How can I access the detailed error logs to get more information about which app and workflow is failing?

In your screenshot, click the "logs" link.

What's the safest deployment strategy to fix this without breaking existing integrations?

You cannot deploy updates without the source code. However, you can make minor app configuration changes that do not change settings that the source code depends on using https://api.slack.com/apps