Custom Webhooks respond with "We could not create the event because the event source is not found"

[Michael James]

I've been added to the custom webhook beta and been trying to set them up.

However, I've hit a bit of a roadblock, when ever I post the information to the webhook it fails with:

The webhook could not be processed: Error calling createEvent in graphql gateway. Error(s): We could not create the event because the event source is not found. Please check that the external event source ID and the type of event being submitted match the event source.If a Forge App ID was used during event source creation, please also check you are using the same Forge App ID when accessing the event source.

Has anyone hit this before have I missed a simple configuration issue?

The message to me suggests that the webhook event source isn't correct but you don't set that, I assume that's inside the webhook code.

My payload is pretty much a 1:1 mapping to the fields needed and I pass the componentId, no mappings etc.

Any advice from other people in the community?

[Patrick Brady]

As a side note, if anyone else is interested in trying out this feature, let us know by following the instructions here https://community.atlassian.com/t5/Compass-articles/Looking-for-beta-testers-Custom-Incoming-Webhook-and-Deployment/ba-p/2870446

[Patrick Brady]

Hey there Michael!

Im a developer on Compass and I'd love to help you debug this situation. Could you send along your atlassian site name so I can help take a look at the logs to identify what might have gone wrong?

This is a great data point for helping prioritize building an invocation history/logs available to end user to help with this debugging, ill bring this to my team :)

Best,

Patrick Brady

[Michael James]

Hi @Patrick Brady it's waterscorporation.atlassian.net 

[Michael James]

I should add, I switched to the GraphQL API and had originally found a few validation issues, and at first thought maybe it was a generic error if an invalid value was provided (one of the ID's in our case wasn't numerical), but I then updated my webhook mechanism to be pretty much the same as the graphql one, and it still failed.

[Patrick Brady]

Gotcha, I took a look at the logs, and I think I have identified a bug on our end. The handling code was not creating the custom webhooks event source since one of the same event type was already attached to the component, even though it was from a different tool. Im going to work on fixing that logic now.

In the meantime, could you try out sending events to a different component without existing event sources? I suspect that will succeed, but just want to be sure I have identified the issue correctly while I work on the fix.

Thank you for your patience and for trying out this new feature! Ill let you know when the fix is live in the next day or so.

Patrick

[Patrick Brady]

Ok, my team has deployed the fix and you should be good to try to send an event to that component again via custom webhooks! Please let me know if you are still experiencing issues.