@MaBeuLux88_xxx, thanks for the welcome and the quick reply!
That’s a good point - I somehow missed the concept of starting the process with “shardsvr” to make it shard aware. The newly added shard does have “state” set, but the original shard (which we deployed years ago) does not.
So, we’ll try to rectify that this coming week and see if it resolves the issue. Thanks for the tip!