I recently created an Incident Workflow which triggers automatically for a service and everything is fine and working no problem.
However, now, I want to add a new kind of workflow that can be triggered manually for that same service, and for some reason, searching that service always returns “No Matches Found”..
Even if I enter into the workflow I that was already created a month or so ago, and “Edit” that service, I can see it populated, but let’s say I remove it and type it again, it will return “No Matches Found”.
If I clone a workflow, the service is populated with no issue, but obviously I need to create a manual trigger and I still encounter the issue.
It’s incredibly frustrating as this is holding up a major change to the way we handle certain incidents, so any advice on this matter would be greatly appreciated.
I've already raised a support request via Chat, but no response, hence I’m here.
Thanks!
Best answer by lupimiguel
Hi @aaronlrobertsww,
I understand a blocker like this can be frustrating. While waiting for support here are a few things you can try that might help you troubleshoot further:
Check your permissions: Make sure you have the right access to the service and that it’s not restricted to a team you’re not part of.
Service eligibility: Confirm the service is active and meets any requirements for manual workflow triggers.
Browser troubleshooting: Try clearing your cache, logging out/in, or using a different browser/incognito mode.
Workflow restrictions: Double-check if there are any limits on assigning the same service to multiple workflows, especially for manual triggers.
Quick workaround: Some users have had luck by renaming the service, saving, and then renaming it back.
If none of these work, it’s likely a bug or a backend config issue that PagerDuty support will need to resolve. I can confirm your support ticket has been created in the system, and I’ve followed with the team to expedite it. If you get a solution from support, please make sure to share it here for others!
I understand a blocker like this can be frustrating. While waiting for support here are a few things you can try that might help you troubleshoot further:
Check your permissions: Make sure you have the right access to the service and that it’s not restricted to a team you’re not part of.
Service eligibility: Confirm the service is active and meets any requirements for manual workflow triggers.
Browser troubleshooting: Try clearing your cache, logging out/in, or using a different browser/incognito mode.
Workflow restrictions: Double-check if there are any limits on assigning the same service to multiple workflows, especially for manual triggers.
Quick workaround: Some users have had luck by renaming the service, saving, and then renaming it back.
If none of these work, it’s likely a bug or a backend config issue that PagerDuty support will need to resolve. I can confirm your support ticket has been created in the system, and I’ve followed with the team to expedite it. If you get a solution from support, please make sure to share it here for others!
