Troubleshooting Automations
Dado's Automations save you and your team a lot of time-consuming manual effort, but they can sometimes encounter obstacles that block them from working. The good news is that these are mostly small problems in the way the relevant integration is set up or little gaps in the data about employees you've given Dado; and they're easy to fix.
All issues Dado encounters with Automations will be displayed in the Issues Bar that appears at the top of your Experience page, along with a suggested fix.
Contents
- Jira: create ticket & Asana: create task
- Google: add to group & Microsoft 365: add to group/team
- Microsoft Outlook/Google Calendar: Invite to event
- Slack & Microsoft Teams: invite to channel
Jira: create ticket & Asana: create task
Problem | Suggested solution |
---|---|
Missing supporting actor Dado needs to add a supporting actor to the ticket/task, but they haven't been set for this Experience. EG: a new hire's manager hasn't been set |
Go to the relevant experience, and select the right person in the dropdown for that supporting actor |
Missing email address Dado looks up users in Jira and Asana by using the work email address you've provided for that person. If Dado doesn't have a work email address, they can't look them up in Jira/Asana, and so can't add them to the ticket/task |
Import a work email address into Dado for that individual |
Can't find this user in Jira/Asana Dado looks up users in Jira and Asana by using the work email address you've provided for that person. Sometimes, an employee's Jira/Asana account will be linked to a different email address. Or they don't (yet) have a Jira or Asana account; this is most common with new hires. |
Create a user for this person in Jira/Asana Or, if a user already exists but has a different email, change the email address in either Jira/Asana or in Dado (via an import). |
Dado has insufficient permissions in Jira/Asana Dado lacks the permissions to create a ticket/task in the relevant project in Jira/Asana. |
Grant the user who set up this integration the right permissions. You can find out who this user is by going to the Integrations page and clicking on Jira/Asana. The email address shown there will match the Jira/Asana user. |
API issues When Dado tried to communicate with Jira/Asana an API issue prevented it. This is usually due to technical issues with the API, or is a momentary failure that soon goes away. |
Dado will automatically retry immediately, then another 5 times, each attempt 10 minutes apart. If this still doesn't work, an issue will appear in the issues bar. Most often, retrying from here works straight away. At other times, you may need to wait until the API issues are resolved by Jira/Asana |
Google: add to group & Microsoft 365: add to group/team
Problem | Suggested solution |
---|---|
Missing supporting actor Dado needs to add a supporting actor to the group/team, but they haven't been set for this Experience. EG: a new hire's manager hasn't been set |
Go to the relevant experience, and select the right person in the dropdown for that supporting actor |
Missing email address Dado looks up users in Google Workspace/Microsoft 365 by using the work email address you've provided for that person. If Dado doesn't have a work email address, they can't look them up in Google Workspace/Microsoft 365, and so can't add them to the group/team |
Import a work email address into Dado for that individual |
Can't find this user in Google Workspace/Microsoft 365 Dado looks up users in Google Workspace/Microsoft Teams/Outlook by using the work email address you've provided for that person. Sometimes, an employee's Google Workspace/Microsoft 365account will be linked to a different email address. Or they don't (yet) have a Google Workspace/Microsoft 365 account; this is most common with new hires. |
Create a user for this person in Google Workspace/Microsoft 365 Or, if a user already exists but has a different email, change the email address in either Google Workspace/Microsoft 365or in Dado (via an import). |
Can't find the group/team This could mean you've misspelled the name of the group/team in the Dado automation. It could be that this group/team really doesn't exist or has been recently deleted. It could also be that Dado has not been granted the right permissions to be able to see a list of groups/teams. |
|
API issues When Dado tried to communicate with Google Workspace/Microsoft 365 an API issue prevented it. This is usually due to technical issues with the API, or is a momentary failure that soon goes away. |
Dado will automatically retry immediately, then another 5 times, each attempt 10 minutes apart. If this still doesn't work, an issue will appear in the issues bar. Most often, retrying from here works straight away. At other times, you may need to wait until the API issues are resolved by Google Workspace/Microsoft 365 |
Microsoft Outlook/Google Calendar: Invite to Event
Problem | Suggested solution |
---|---|
Missing supporting actor Dado needs to add a supporting actor to the group/team, but they haven't been set for this Experience. EG: a new hire's manager hasn't been set |
Go to the relevant experience, and select the right person in the dropdown for that supporting actor |
Missing email address Dado looks up users in Google Workspace/Microsoft 365 by using the work email address you've provided for that person. If Dado doesn't have a work email address, they can't look them up in Google Workspace/Microsoft 365, and so can't add them to the group/team |
Import a work email address into Dado for that individual |
Can't find the event This could mean you've misspelled the name of the event in the Dado automation. It could be that this event really doesn't exist in the calendar you've specified, or it has been recently deleted/moved to another calendar. |
|
API issues When Dado tried to communicate with Google Calendar/Microsoft Outlook an API issue prevented it. This is usually due to technical issues with the API, or is a momentary failure that soon goes away. This could also be caused by Dado lacking the right permissions to access the calendar specified in the Automation. |
|
Slack & Microsoft Teams: invite to channel
Problem | Suggested solution |
---|---|
Missing supporting actor Dado needs to add a supporting actor to the channel, but they haven't been set for this Experience. EG: a new hire's manager hasn't been set |
Go to the relevant experience, and select the right person in the dropdown for that supporting actor |
Missing email address Dado looks up users in Slack/Microsoft Teams by using the work email address you've provided for that person. If Dado doesn't have a work email address, they can't look them up in Slack/Microsoft Teams, and so can't add them to the channel. |
Import a work email address into Dado for that individual |
Can't find this user in Slack/Microsoft Teams Dado looks up users in Slack/Microsoft Teamsby using the work email address you've provided for that person. Sometimes, an employee's Slack/Microsoft Teams account will be linked to a different email address. Or they don't (yet) have a Slack/Microsoft Teams account; this is most common with new hires. |
Create a user for this person in Slack/Microsoft Teams Or, if a user already exists but has a different email, change the email address in either Slack/Microsoft Teams or in Dado (via an import). |
Can't find the channel This could mean you've misspelled the name of the channel in the Dado automation. It could be that this channel really doesn't exist; or just that the Dado app has not been given access to it. |
|
This person isn't a member of the relevant team [Microsoft Teams only] Dado can only add people to a shared channel in a Team, if they are already part of that Team. |
|
API issues When Dado tried to communicate with Slack/Microsoft Teams an API issue prevented it. This is usually due to technical issues with the API, or is a momentary failure that soon goes away. |
Dado will automatically retry immediately, then another 5 times, each attempt 10 minutes apart. If this still doesn't work, an issue will appear in the issues bar. Most often, retrying from here works straight away. At other times, you may need to wait until the API issues are resolved by Slack/Microsoft Teams |