Hubble castsByParent unexpected behaviour with reverse param

[savish28]

What is the bug?
A concise, high level description of the bug and how it affects you
Hubble's castByParent HTTP endpoint returns an error with certain url params when reverse parameter is 1, works fine without reverse

How can it be reproduced? (optional)
v1/castsByParent?url=https%3A%2F%2Fwarpcast.com%2F~%2Fchannel%2Ftalent&reverse=1

returns

{
"errCode": "not_found",
"presentable": false,
"name": "HubError",
"code": 2,
"details": "could not get message with key: [1, 181, 227, 3, 250, 1, 112, 114, 111, 116, 111, 99, 111, 108, 6, 154, 117, 255, 187, 238, 129, 122, 84, 254, 17, 198, 78, 15, 145, 60]",
"metadata": {
"errcode": [
"not_found"
]
}
}

Additional context (optional)
Add any other context about the problem here.
Works fine with v1/castsByParent?url=https%3A%2F%2Fwarpcast.com%2F~%2Fchannel%2Ftalent

[sds]

Hey @savish28, this was reported in #2067 and we thought we fixed it in #2077, which was released in Hubble 1.13.3.

However, as you point out, introducing the reverse=1 param seems to break things. Adding @Wazzymandias since they might have context.