Jira connect app webhook not being recieved for some users

[Joe Hakim]

I'm having an issue where webhooks we've defined in a connect module for a Jira app https://developer.atlassian.com/cloud/jira/platform/modules/webhook/ aren't being delivered, but only when non-admin users trigger the events related to the webhook (e.g. `

jira:issue_created`). I'm trying to debug whether they're not firing on the Jira side, being sent to the wrong address, etc., however I can't find any way to query either the existing defined webhooks or the failed-to-deliver webhooks. 

Note that I've tried using the REST api from within the app to query these (e.g. GET /rest/api/3/webhook and GET /rest/api/3/webhook/failed), although these return empty lists (probably because these look for *dynamic* webhooks as opposed to those defined in a connect descriptor).

Is there any way to get a log of webhooks defined as part of a connect module, as opposed to dynamic webhooks?

Thank you!

[Jan Pöschko]

Not an answer, but elaborating on the problem:

It seems to be even less deterministic than this. Sometimes webhooks don't fire for admin users, either, and sometimes they work for other users. We don't see any trace of the missing request in our web server logs, so it really seems as if Jira didn't even make those requests. They don't show up in `/webhook/failed`, either (https://stackoverflow.com/questions/71311973/how-to-query-jira-webhooks-defined-in-descriptor-of-atlassian-connect-app).

So the overall problem is sporadic webhook delivery with no way to debug why they're not delivered.