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
If the bot knows that there was a Bot <-> HS error (as it seems from some comments of #844), should the error appear in the Integrations Manager dialog?
Maybe having an error under Recent feed results, in addition to Successful fetch, would help discover and report any failures in the future.
I don't know if it is feasible? The dialog is loaded from integrations.ems.host, not the HS, so a failure to send to the HS can be logged somehow?
The text was updated successfully, but these errors were encountered:
The problem is in theory even Bot <-> HS errors should be retried, and they should be invisible ideally. I'm worried about bubbling up operational problems like homeserver flakiness to the user, whereas the feed fetch failures are more understandable to the user.
Not pushing, just throwing an idea up in the air.
If the bot knows that there was a Bot <-> HS error (as it seems from some comments of #844), should the error appear in the Integrations Manager dialog?
Maybe having an error under
Recent feed results
, in addition toSuccessful fetch
, would help discover and report any failures in the future.I don't know if it is feasible? The dialog is loaded from
integrations.ems.host
, not the HS, so a failure to send to the HS can be logged somehow?The text was updated successfully, but these errors were encountered: