You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem receiving events via webhooks.
My purpose is that every time the answer to a question (that is a suggestion of a model) is changed from the argilla UI, my server receives an event indicating that it has been changed.
I have argilla up locally through a docker with the configuration uploaded in this repository.
Below I provide the code I use for the argilla upload and webhook configuration.
When I launch the server, I access argilla to see the dataset records. I want that when I change the suggestion of one of them and press send, I receive the event
Environment
Docker with same configuration as indicated in this repository
Additional context
No response
The text was updated successfully, but these errors were encountered:
AnaAbadLorenzo
changed the title
Unable to receive events via Webhooks
[BUG] Unable to receive events via Webhooks
Jan 20, 2025
Can you verify the webhook server is up and running at http://localhost:8000? Also, can you share some env info (OS, docker version, ...)? It looks like a network error, but I cannot determine the origin.
Describe the bug
I have a problem receiving events via webhooks.
My purpose is that every time the answer to a question (that is a suggestion of a model) is changed from the argilla UI, my server receives an event indicating that it has been changed.
I have argilla up locally through a docker with the configuration uploaded in this repository.
Below I provide the code I use for the argilla upload and webhook configuration.
Stacktrace and code to create the bug
I launch de application with
When I complete a record suggestion, I obtain this error
Expected behavior
When I launch the server, I access argilla to see the dataset records. I want that when I change the suggestion of one of them and press send, I receive the event
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: