"No Valid Delivery Channel: NO_CHANNELS" in the logs?

Open Q&A
,
1

Courier’s logs say this is what I sent to the API:

{
  "event": "FVFV2Q7C4W4GXVHV92PJJPNM3BCK",
  "recipient": "redacted@example.com",
  "data": {
    "world": "Ruby!"
  }
}

And I am seeing this error in the logs:

{
  "reason": "No Valid Delivery Channel",
  "type": "NO_CHANNELS"
}
2

In this case no profile was added to the original API call, and Courier didn’t find a matching profile for the redacted@example.com recipient ID. Changing the call to this should work:

{
  "event": "FVFV2Q7C4W4GXVHV92PJJPNM3BCK",
  "recipient": "redacted@example.com",
  {
    "email": "redacted@example.com"
  },
  "data": {
    "world": "Ruby!"
  }
}
1 Like
3

We should improve our error messaging here. If no channels matched AND the profile is empty, we should instead start returning:

{
  "reason": "No Profile",
  "type": "NO_PROFILE"
}