thanks lvlinux; no doubt. actually the first thing I chased up was flush'ing the cache; then later I did also restat all the kz apps. Same sticky outcome. We had taken a couch node out of service earlier in the week and this accidentally created some holes in our dataset. my current speculation is that having that gap created some kind of issue. I worked around by recreating the account, fortunately,

it only had a single faxbox and DID.

gontran: ah yes, removing a CouchDB node would remove some data, and potentially have a partially accessible document---i.e. one that was read-only, or possibly only returned sometimes (due to the cluster quorum settings).

on the 2600hz partner call right now; reads like the app marketplace is going to beta testing with limited partners as of today. Need to be running 5.1....

lvlinux: probably it; the fact that it's not accessible now, I think has to do with all the poking at it I did.

re marketplace, also running a (hosted) cluster instance appears to be required.