Troubleshooting Workbot for Slack

Sometimes when interacting with Workbot, he may raise some errors or issues. Here are some common errors and issues that Workbot might tell you about, and how to handle them.

Recipe execution error

Workbot is powered by Workato recipes to fetch your app data, such as retrieve Salesforce opportunities' data, or to write data to your apps, such as creating a new account in Salesforce. When Workbot tries to execute your command, but meets with an unexpected error, he will respond with the following message.

Workbot error message about recipe execution error

Usually, there is also a short description included about the error. To fix this error, you will have to go to the recipe, look for the failed job, and debug the error that happened in the job.

Workbot offline

At times, you may find that despite having an active recipe or connection, Workbot appears to be offline. This is usually temporary - he might be undergoing maintenance, or gone out for a coffee break!

Occasionally, reconnecting your Workbot connection helps to get him back online. Reconnect just like how you would reconnect to Slack. Navigate to Connections, find the Workbot connection, disconnect, and connect again.

Navigate to Connections and reconnect to Workbot

Custom bot recipe not triggered

You may encounter an error where invoking the command of the custom bot doesn't trigger a recipe.

Follow these troubleshooting methods to resolve the issue:

1

Go to Tools > Custom OAuth profile and select the profile for your custom bot.

2

Copy the request URL that contains /actions. For example, ​https://app.workato.com/slack_webhooks/actions?coak_id=9670.

Request URL

3

Ensure that the request URL in the Interactive Components section of your Slack API app matches the one in your Workato custom OAuth profile. Update the configurations to the same request URL if they don't match.