Message unacked when Trigger Engine failes to connect to the target #936
Labels
app:trigger_engine
This issue or pull request is about astarte_trigger_engine application
bug
Something isn't working
Observed first in Astarte 1.0.4, but a similar behavior is still present in Astarte 1.1.1
It was observed by installing a trigger with an HTTP action on a local kubernetes DNS service without specifing the port
Without the port, the service could not be reached making Trigger Engine crash.
The following log is from Astarte 1.1.1
The text was updated successfully, but these errors were encountered: