> ## Documentation Index > Fetch the complete documentation index at: https://docs.superember.ai/llms.txt > Use this file to discover all available pages before exploring further. # Common issues > Troubleshoot SuperEmber setup, Slack, agents, tools, workflows, and workspace files. Use this page before escalating an issue. ## Slack Is Not Connected Check: * you are signed in to the correct SuperEmber account * you selected the correct Slack workspace * you have permission to install Slack apps * the connect page shows Slack as connected * the agent is not still provisioning ## SuperEmber Does Not Reply In Slack Check: * SuperEmber is installed in the workspace * SuperEmber has access to the channel * you mentioned SuperEmber directly * the message is not only visible in a private channel where the app was not invited * included usage has not been reached ## Agent Is Stuck Setting Up Provisioning usually completes quickly, but it can take longer during load or account setup. Try: * refresh the dashboard * wait a minute and check again * retry provisioning for draft fleet agents * confirm the account has not hit resource limits ## Connectors Are Unavailable Check: * the selected agent is active * the connector feature is enabled for the workspace * the connector authorization flow completed * the connector was connected to the intended agent * the connector has not expired ## Skill Or MCP Changes Do Not Show Up After saving runtime changes, SuperEmber loads the updated configuration on the next message or after a runtime restart. If it still does not show: * refresh the installed list * verify the agent is active * check the JSON configuration * remove and reinstall the item if needed ## Model Change Does Not Apply Check: * you changed the model for the intended agent * the value is a valid supported chat model slug or suggested alias * you used `/model default` if you wanted to clear the override * you sent a new message after changing the model In shared channels, `/model` changes the selected shared agent, not only the person who typed the command. ## Wiki Memory Is Unavailable Check: * wiki memory is enabled for the workspace * you are signed in to the correct account * the dashboard route is not hidden by workspace policy * the page path is valid lowercase markdown-style path text If semantic recall is unavailable, SuperEmber can still use full-text wiki recall when the wiki store is healthy. ## Workflow Will Not Publish Publishing can fail when validation or governance blocks the package. Check: * every node has required configuration * required bindings are mapped * trigger configuration is valid * high-risk steps are intentional * governance allows the operation * the workflow has a valid path from trigger to steps ## Workflow Run Is Waiting Open the workflow inbox. The run may be waiting for approval, input, a choice, a channel reply, a callback, an agent result, a fleet join, or a delay. ## Delegation Does Not Start Check: * the target is a direct eligible report in Fleet * both source and target agents are active * delegation is enabled for the workspace * the request names a bounded task and a valid target * the target team's access rules allow the caller If no Main channel is configured, ordinary delegation may use a headless fallback. Configure Main when the team needs visible operation threads and human escalation. ## Delegated Work Is Waiting For Review The target specialist proposed an exact action that automatic review could not safely approve. Open the target team's Main operation thread and inspect the approval prompt. Nothing has changed yet. Approve only when the exact tool, account, target, arguments, and effect are correct. If the source thread says the team could not be notified, assign a Main channel. The action remains paused; do not ask the source agent to restate the same action as a workaround. ## An Action Was Denied Automatically A denial means the proposed boundary action did not execute. Ask the agent to choose a materially safer route, narrow the scope, or return a draft for human review. Rephrasing or splitting the same action to bypass review is not supported. Repeated denials in one turn escalate to a human decision. ## Workspace Files Are Unavailable Check: * the agent is active * workspace access is enabled * the file path exists * the runtime workspace is reachable If the file is a final deliverable, ask SuperEmber to save it clearly and then promote it to an artifact after review.