You can find our new documentation site and support forum for posting questions here.
Monitor claims "Call caching: Disabled" erroneously
In the first few seconds of a submission (before it actually gets going) the Monitor will state that a certain submission has Call Caching disabled even though this isn't true.
A frantic refresh will eventually correct this, but I've nearly aborted a few submissions due to this message. It would be better to say "n/a" or leave blank is the correct answer is not known than to state something which is untrue.