gluster volume bitrot <volname> scrub status - request timed out?

[edrock200]

I'm not sure if this is a bug or if I'm doing something wrong, so figured best to ask here first before posting in issues section. I have a dispursed gluster volume setup with bitrot enabled, throttle set to lazy, and scheduled for monthly scrubs. I can pause and resume the scrubber without issue successfully. However, if I try gluster volume bitrot scrub status (where is the name of my volume) it hangs at the prompt for a min then says request timed out. For several minutes after this, if I try any bitrot commands, it tells me gluster is busy processing another request, which I'm guessing is my bitrot status command. After 5m or so, I can once again execute bitrot commands, but I can't ever seem to get a status on it for some reason.

At first I thought I was trying status too soon after resuming a scrub, but the next time I tried waiting 30m or so, and same result. Looking at bitd.log, I don't see anything obvious, but I'm no expert either. Am I doing something wrong, is this expected behavior, something else? Thanks in advance for any help/guidance.