Webhooks are not displayed and cannot be edited

Unfortunately, I am currently having problems on some webhooks that cannot be displayed, let alone edited.

There are also some webhooks affected that were not newly created, but I cannot recognize a pattern.

In my case, the webhooks point to the Opensemap.

Who should I contact to have a look there and what information is required?

We’re sorry!

There was a problem when displaying this section
If the error persists, please contact an administrator.

5 Likes

I was able to fix the problem myself, just added a new application, new end device, payload decoder and created a new webhook, then it worked again…

Thanks for your time even if there was no answer. :slight_smile:

We have exactly the same same problem.

Any news on this? Having the same issue but have to many devices to really spend the time to re-create the application

There was little information provided in the original post to go on, so when you (@SCALE-TTN & @oscarresebo) say you have the same issue, can you say what your issue actually is.

@oscarresebo, if you have too many devices, maybe a TTI instance would be a better option - @rish1 can help!

Yes sorry. The issue here is that when trying to view a webhook in the user interface. I always get this error message as @HTW-Informatik-AG post above:

We’re sorry!

There was a problem when displaying this section
If the error persists, please contact an administrator.

So i can see a list with my webhook, but when clicking it (to see and edit settings), I always get this error message. I´m not sure if it helps but there is a “React Minifed Error”: Too many re-renders. React limits the number of renders to prevent an infinite loop. Indicating that something is crashing in the UI. I can still access my webhooks and its content via the CLI, but the UI would be a bit more convenient.

I think that gives us some concrete info to pass over to the TTI team. I’ll put it on Slack.

2 Likes

I seem to be experiencing a similar issue. I accidentally copied and saved a wrong URL in a Webhook. Afterward, a device in the application sent multiple times, which caused errors. Since then, I’ve also been getting the error message and can’t correct the URL.

1 Like

Hi everyone,

I seem to be experiencing a similar issue. I’ve configured a few webhooks, but some of them show the status “Requests failing”. Which might be due to a typo or misconfiguration on my end. However, the problem is that I can’t access the configuration page of these webhooks to make any corrections.

Interestingly, for webhooks that show “Healthy” or “Pending”, I can open the configuration page and update the settings without any issue.

This is what I’m observing on my end, and I hope this helps clarify or contribute to the discussion.

1 Like

Same issue here. When a webhook failed due to worn URL, i got stuck and cannot delete or edit it anymore.

I have the same issue. Cannot kill the wrong webhook. Get the were sorry error posted above.

what also is going on is that webhook I cannot get into is running and failing because of a wrong url. I created a 2nd new webhook and it isnt working. its like that one I cannot get into has hijacked everything and preventing the other from running.