You can enable debugging commands in your production environment if you need to troubleshoot an issue.
Jump to: Enable debugging commands.
Debugging commands
To use the debugging commands, type the commands in the channel you're troubleshooting, just like a question to your chatbot. Debugging commands are not case-sensitive, but passage IDs and conversation IDs are case-sensitive.
| Command | Description |
|---|---|
| restart | Restart the chatbot by putting the current user into the welcome passage of the starting conversation. |
| jump to {Passage ID} |
Jump to the specified passage within the current conversation. If you need to jump to a passage in a different conversation, use the start conversation command first to switch the conversation. Note: Starting a passage with the jump to command will be reflected in your Mixpanel reports. |
| switch conversation {conversation ID} |
Switch to the specified conversation. This does not start any passage in that conversation. If you want to start a passage after switching conversations, use the jump to command. |
| reset intellimem | Reset the user's intellimem status so the chatbot "forgets" any responses it has already sent to the current user. |
Enable debugging commands
Only for troubleshooting
To prevent users accidentally impacting the flow of your chatbot, you should only enable debugging commands when you're actively troubleshooting an issue.
To enable debugging commands:
- Select your team, and the chatbot you want to edit.
- Open the Manage section of the left navigation and click Settings.
- Select Enable Debug Commands.
- Click Save.
Comments
Article is closed for comments.