7.5.1 - Application not getting/showing response on trigger of event

[Neel1]

i did following steps but application  not getting/showing response on trigger of event.

1. From swagger, i am able to successfully able to get Subscription ID & subscriptions. passed the body like this

{
"callbackUrl": "URL",
"eventTypes": ["completed", "exception"],
"callbackSecretHeader": "value",
"callbackSecret": "Value!$"
}

2. The webhook subscription is visible under Active Subscriptions.

3. When I mark the item as Exception in Blue Prism, the webhook entry disappears from Active Subscriptions.

4. However, the target application does not receive or display any callback response.

Advise if I am missing any configuration or validation steps?

#7.5.1

[hossein.azimi]

Hi Nell1

Thanks for the contacting Blue Prism Community.

I would suggest the following to narrow down the issue.

First, a quick clarification: the webhook subscription disappearing from Active Subscriptions right after you mark the item as Exception is actually expected behavior. A subscription automatically moves to Inactive once the event reaches a final state (Completed or Exception), regardless of whether the callback was successfully delivered to your application. So this isn't a symptom of something being broken — it's the platform working as designed.

That said, the fact that your application isn't receiving anything does point to an issue with the callback delivery itself. Could you check the following on your end and let us know what you find?

1. Inactive Subscriptions view — Please check this screen (not just Active Subscriptions) for that subscription. It should show the last known status, e.g., "Failed." This will tell us immediately whether Blue Prism attempted delivery and failed, or something else is going on.
2. Webhooks enabled globally — Please confirm the "Enable Webhooks" (or "Enable Webhook functionality," depending on your version) setting is switched on at the system level. If it's off, subscriptions remain visible but callbacks are never sent.
3. Server connection type — Webhooks require Blue Prism Enterprise to be connected via a Blue Prism Server connection. Could you confirm this is how your environment is set up?
4. Authentication setup — In addition to the callbackSecret/callbackSecretHeader fields in your subscription request, Blue Prism Enterprise requires either a digital signature (via a default encryption scheme configured for the client application) or basic authentication (via a credential created for the client application) to be set up separately. If this isn't configured, or your application returns a 401/404 in response, Blue Prism will not retry — it fails immediately and the subscription drops to Inactive, which matches what you're seeing.
5. Network access from the Blue Prism Server host — The callback is sent from the Blue Prism Server machine itself, not from your local workstation. Could you confirm that machine has outbound network access to your callback URL (firewall rules, DNS resolution, etc.)?
6. Application-side logs — Please check your receiving application's web server logs for any incoming request around the time you triggered the exception — even a rejected request (401/404) should appear there and would confirm whether Blue Prism attempted delivery at all.

Once you've checked the Inactive Subscriptions status and your app-side logs, this can pinpoint whether this is an authentication issue, a network/firewall issue, or something else.

Regards
Hossein Azimi (APJ  team)

[Neel1]

Hello @hossein.azimi Thank you for sharing the inputs. Please find my responses below:

1. In the Inactive view, I can see that the Run Status is showing as Failed.
2. The configuration is enabled.
3. The connection type is Server Connection.
4. Default encryption is configured. The Work Queue (WQ) is also encrypted using the same setup.
5. This has also been configured correctly.
6. I have not yet checked this and will review this.