Last week I happened to be using a Decoder for some test and noticed a timeout for 0.5% of the messages (6 out of 1,238 = 0.005), during the 15 hours of that test:
Note that this also delays delivery of the message through MQTT or HTTP with the timeout shown in the error.
I’m currently not using it, so I don’t know if that was a temporary glitch or not. But when I reported in the #ops channel in Slack it seemed this is quite common, every now and then:
@mat89 2020-08-23 12:24 AM
I had a similar issue some time ago, not getting decoded payload through the http integration.
I then programmed my own payload decoder but I never activated it…
Haven’t had missing decoded payload since a while
@jpmeijers 2020-08-23 02:38 PM
I’ve seen this happening on some of my data too a while back. Not critical for most cases when one decode your payload yourself, but ttnmapper.org depends on this to work.