Closed rivlinpereira closed 2 years ago
@rivlinpereira is there an error in the server logs that you can share? Did you configure the pagerduty or opsgenie plugins?
Using pagerduty plugin configured via UI. The only logs i see from the slack container are -
ERROR:slack_sdk.socket_mode.aiohttp:Failed to run a request listener: 'email', session: s_xxxxxxxx
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/slack_sdk/socket_mode/async_client.py", line 156, in run_message_listeners
await listener(self, request) # type: ignore
File "/usr/local/lib/python3.9/site-packages/dispatch/plugins/dispatch_slack/socket_mode.py", line 36, in process
response = await handle_slack_event(
File "/usr/local/lib/python3.9/site-packages/dispatch/plugins/dispatch_slack/events.py", line 133, in handle_slack_event
user_email = await dispatch_slack_service.get_user_email_async(client, user_id)
File "/usr/local/lib/python3.9/site-packages/dispatch/plugins/dispatch_slack/service.py", line 202, in get_user_email_async
return user_info["profile"]["email"]
KeyError: 'email'
Sounds like you were able to resolve it based on this discussion? Feel free to close the issue if so.
Sounds like you were able to resolve it based on this discussion? Feel free to close the issue if so.
yes but now facing another issue. closing this one
Describe the bug See the following error when I try to engage the on-call person from a private channel that dispatch creates
Sorry, we've run into an unexpected error. For help please reach out to your Dispatch admins and provide them with the following token: xxxxxxxxx
To Reproduce Steps to reproduce the behavior:
Expected behavior The /dispatch-engage-oncall should work
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.