NIS api: harvesting status locked, not coherent

Tech Support
#1

Hi,
I called:
:7890/account/get?address=

passing an active harvesting supernode address
(I saw harvested blocks incremented
today).
Json returned was:

{"meta":
 {
  "cosignatories":[
  {"address":"...",
   "harvestedBlocks":0,
   "balance":1000000,
   "importance":0.0,
   "vestedBalance":1000000, 
   "publicKey":"...",
   "label":null,"multisigInfo":{}},
  {"address":"...",
   "harvestedBlocks":4,
   "balance":56087004208,
   "importance":1.7587817350333336E-5,
   "vestedBalance":15103882012,
   "publicKey":"...",
   "label":null,
   "multisigInfo":{}},
  {"address":"...",
   "harvestedBlocks":0,
   "balance":0,
   "importance":0.0,
  "vestedBalance":0,
  "publicKey":"...",
  "label":null,
 "multisigInfo":{}}],

  "cosignatoryOf":[],
 "status":"LOCKED",
 "remoteStatus":"ACTIVE"},
 "account":{"address":"...",
 "harvestedBlocks":630,
 "balance":3119045398290,
 "importance":3.1885975870939685E-4,
 "vestedBalance":3116121630678,
 "publicKey":"...",
 "label":null,
 "multisigInfo":{
 "cosignatoriesCount":3,
 "minCosignatories":2}}}

According to NIS documentation
the harvesting status on metadata means:
“LOCKED”: The account is not harvesting.

Well the account is actually harvesting, that’s either documentation
bug or something…

#2

I’m not sure but maybe you should look at remoteStatus if your account have activated remote delegated harvesting?
https://docs.nem.io/en/nem-dev-basics-docker/account-requests

“ACTIVE”: The account has activated remote harvesting and remote harvesting is active.