# Connection status and troubleshooting

## Connection states

Open **Two-way messaging** to check the connection's current state.

| State | Meaning |
| --- | --- |
| Connecting | The connection is being established |
| Connection established | The connection to the platform is open |
| Reconnecting | The connection was interrupted and MOI is attempting to restore it |
| Credential verification failed | The platform rejected the credentials; check them and save again |
| Connection configuration invalid | The configuration is incomplete or invalid; correct it and save again |
| Connection stopped | The connection has been stopped and MOI is no longer receiving messages through it |
| Waiting for the first message | The first platform message has not arrived; also check the connection and receiving indicators |

The dialog also shows configuration and receiving indicators:

| Indicator | Meaning |
| --- | --- |
| Configuration saved | The settings were saved; a connection may not yet be established |
| MOI receiving enabled | Receiving is enabled; this does not confirm that a message has arrived |
| Waiting for the first real message | No real message has been received through this connection; send a test message to the connected bot |
| Real message received | MOI received an incoming message; agent execution or reply delivery may still fail |

To verify the complete flow, check **Connection established**, then **Real message received**, and confirm that the agent replies in the original messaging conversation.

## Common problems

| Symptom | What to check |
| --- | --- |
| Credential verification failed | Check that the Secret, App Secret, or token matches the platform's current value. When editing a connection, blank means keep the current value; enter a new value and save to replace it. |
| Stuck on Connecting or Reconnecting | Reopen the dialog and check the state and connection error. Correct invalid credentials or configuration and save again. |
| Connected, but still waiting for the first real message | Check that you sent the message to the connected bot. Check app availability, message-event subscriptions, and receiving permissions. Mention the bot in a group. |
| Real message received, but no reply | Open the corresponding MOI conversation and check the runtime model and task result. If MOI generated a reply, check platform sending permissions and reported delivery errors. |
| Feishu messages do not reach MOI | Check that the app is published, receives events through a long-lived connection, subscribes to the receive-message event, and has permission to receive the relevant direct or group messages. |
| Slack messages do not reach MOI | Check that the app is installed to the correct workspace and the bot has joined the channel. Direct messages need `message.im` and `im:history`; channel mentions need `app_mention` and `app_mentions:read`. |
| The agent cannot read an incoming file | Check that the platform lets the bot download the file. Slack requires `files:read`. Also check file type, size, and reported errors. |
| A generated file does not arrive | Confirm in MOI that the task generated the file. Check platform sending permissions and file limits; Slack requires `files:write`. |
| A `!moi` command has no effect | Send the command separately and check its arguments. Switch and rename commands use a session ID from `!moi list sessions`; renaming also requires a new name. |
| New messages are not received after disconnection | Enable the connection again, test it, and check the current session. Check tasks for messages already received in MOI. |
| No response in a group | Mention the bot and check that it is a member of the conversation. Direct messages do not require a mention. |

## Next steps

- [Two-way messaging](index.md)