NRF Cloud Message Routing Service not sending payload in device data message

[Clinto]

Hi,

I have set up a destination in the the NRF Cloud Message Routing Service

The destination has been verified and I can successfully send the test message from NRF Cloud and receive the message and payload at the destination. All good there.

However, when my devices send data to NRF Cloud, NRF Cloud forwards the message to the configured destination without a payload. I can seen the message being received at the destination by no JSON.

Example of received test message and device data (empty)

When I send a simulated nrf cloud payload - As shown in the Message Routing Service documentation - the destination accepts the message without error.

NRF Clouds also shows there have been 0 message failures

How can I check what data is being sent to the destination? 

Is there any reason why empty payloads are being sent?

[Markku Lehto]

Hi Clinto,

thank you for your patience. I will direct this to internal development team. One more thing to ask, could you give an example of message content that was not sent out via Message Routing Service? So you saw it in message store, but it was sent through Message Routing Service as an empty message. Also, related to this, are you seeing this consistently, so that none of your messages have content, or just some of the messages are empty?

Best regards,

Markku Lehto 

[Clinto]

All message content is not being sent out via Message Routing Service except the test function that is available of the Message Routing Service setup page.

Consistently all messages are empty.

an example message from the message store than comes through empty:

{
        "topic": "prod/xxxxxxxx-xxxx-4f2f-xxxx-5a299abxxxxx/m/d/xx-xxxxxxxxx541592/d2c",
        "deviceId": "xx-xxxxxxxxx541592",
        "receivedAt": "2025-05-09T04:49:20.964Z",
        "message": {
            "appId": "BATTERY",
            "messageType": "DATA",
            "ts": 1746766158744,
            "data": 100
        },
        "tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx98e1"
    },

[Clinto]

any further developments of why the message service routing doesn't work?

[Juha-Pekka Kesonen]

Hi, I tried to reproduce the empty message with multi service sample but wasn't able to, can you give any more information on the setup and can you see the message logged on the serial terminal when sending the failing message?

[Clinto]

There is not problem sending data between the device and nrfcloud using the multiservice sample.

nrfcloud is confirmed to be receiving data from the device and storing the content in the message list (described above)

test connections sent from nrfcloud Message Routing Service endpoint to the destination work fine - http message received and json payload ok

The problem is when the device sends a new message to nrfcloud - the Message Routing Service attempts to forward the message to the destination but without the json payload/data (its empty). 

 

None of the messages are failing as all messages are being sent between all endpoint. The problem is DATA messages are being sent between nrfcloud and the destination with no data.

Does this help clarify the problem?