[BUG] message: "failed to execute message; message index: 0: dispatch: submessages: nil message field: unknown request

[taariq]

Paloma upgraded to v2.4.1 today.

Running Nodesale contract job gave the error while using the Paloma SDK.

Code line: https://github.com/VolumeFi/paloma_nodesale/blob/main/node-licenses.js#L1096

Cosmwasm Contract: https://github.com/VolumeFi/paloma_nodesale_cw

LCD Server: https://api-1.paloma.nodes.guru/ (upgraded to Paloma v2.4.1)

message: "failed to execute message; message index: 0: dispatch: submessages: nil message field: unknown request [/home/aptostake/paloma/x/scheduler/bindings/msg_plugin.go:40] with gas used: '134677'".

[taariq]

@fullstack412 from @byte-bandit
Thanks for bringing this to my attention. Just to confirm and triple check: the nodesale infrastructure worked fine before the upgrade, and no changes were made to the JS backend or the CW contract? - Correct.

I did some digging earlier and it looks like those messages hit the wrong handler, but I don't yet see why. It's possible that we will need to change the way jobs are executed as well - which would mean updating and redeploying all CW contracts as well. So I'll try every other option first and see if I can make it work.

[taariq]

@byte-bandit added the CW contract to the ticket.

[byte-bandit]

Closed with palomachain#1325

[taariq]

@webelf101 @byte-bandit when testing today, we have the same issue

data: {

Jan 13 14:20:10 bots-server start.sh[148425]: code: 2,

Jan 13 14:20:10 bots-server start.sh[148425]: message: "failed to execute message; message index: 0: dispatch: submessages: nil message field: unknown request [/home/aptostake/paloma/x/scheduler/bindings/msg_plugin.go:40] with gas used: '134677'",

Jan 13 14:20:10 bots-server start.sh[148425]: details: []

Jan 13 14:20:10 bots-server start.sh[148425]: }

[taariq]

closing. we are TWO hours too early.