Thanks for getting in touch. We had a chat about this and we feel it’s by-design as it is.
Suppressing further issues seems like just an extra feature and it would need to be opt-in. If you’d like to make more of the case for the feature post it on https://octopusdeploy.uservoice.com/ and we can see if gets traction with the community.
Whilst I understand where you and the team are coming from having half a dozen identical failure guidence events is a little unhelpful.
When using parallel deployments, it’s possible that you can have multiple events at the same time.
Perhaps instead the event should give context as to the step/action which triggered the failure guidence?
As currently on parallel deploys the feature is rather annoying as you don’t know the failed step, so can’t decide which action to take.
That is a good suggestion and we could frame it as a general enhancement to subscription events, along the lines of "Show more metadata on subscription events" and give your case as an example.
Unfortunately it’s not a one-day task. If you can please raise it on uservoice, it will allow us to gauge interest and balance it against our other priorities.
The owner of the subscription feature is on holiday now, I’ll make sure they see this suggestion when they get back.