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 enabled the webhook in the integration setting, with the correct URL set :
Then I tested it by adding more feed, but nothing happened, I'm not receiving any calls on my API service end.
Then I turned on the debug log for miniflux, and didn't see any mention of webhook outgoing calls, let alone an error reported (for the case my API or URL is incorrect). So I think this is more likely a problem on miniflux's side.
Webhook events are sent only for new entries during a feed refresh. The logs you shared seem to be related to the feed creation process, as indicated by this line: msg="Begin feed creation process from subscription discovery".
Webhook events are sent only for new entries during a feed refresh. The logs you shared seem to be related to the feed creation process, as indicated by this line: msg="Begin feed creation process from subscription discovery".
Shouldn't the creation process considered "new_entries" events too? Since most of the time it will pull new entries upon creation (mine did). Or maybe the question is why that pull-new-entries-upon-creation didn't trigger the event?
Shouldn't the creation process considered "new_entries" events too? Since most of the time it will pull new entries upon creation (mine did). Or maybe the question is why that pull-new-entries-upon-creation didn't trigger the event?
I have enabled the webhook in the integration setting, with the correct URL set :
Then I tested it by adding more feed, but nothing happened, I'm not receiving any calls on my API service end.
Then I turned on the debug log for miniflux, and didn't see any mention of webhook outgoing calls, let alone an error reported (for the case my API or URL is incorrect). So I think this is more likely a problem on miniflux's side.
Here are the logs:
I checked the webhook settings afterwards, it remains checked and url set.
The text was updated successfully, but these errors were encountered: