Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Too many pagerduty schedules causes /incident pager command to time out #470

Open
ImDevinC opened this issue Mar 8, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@ImDevinC
Copy link
Contributor

ImDevinC commented Mar 8, 2024

Describe the bug
We have 16 schedules in PagerDuty, and when we run /incident pager the command times out. In the log I see the following messages

PagerDuty returned 15 schedules
Error: The request to the Slack API failed. (url: https://www.slack.com/api/views.open) The server responded with {'ok': False, 'error': 'expired_trigger_id'}

Version
1.10.1

To Reproduce
Steps to reproduce the behavior:

  1. Create 15 schedules in PagerDuty
  2. Type /incident pager

Expected behavior
Modal should popup

Environment (please complete the following information):

  • Platform: Kubernetes

Additional context
I'm not 100% sure that 15 schedules causes it, could be the number of users per schedule or something else

@ImDevinC ImDevinC added the bug Something isn't working label Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants