The client can’t post a report if it’s not connected to a Relay so first check that the most-recent Relay Select was successful.
Next I’d check the section “If the client is posting reports, but much less frequently than expected; is receiving GatherHashMV messages, but is slow to execute or report back Analysis results, there may be long-running evaluations” above.
If you have a number of properties set to evaluate “Every Report”, then the report won’t post until those have evaluated. If, combined, they take five minutes, or ten, or twenty, then it will take the client that long to evaluate before each report is posted. I’d use the Analyses I reference, along with BES Client Debug Logging, to see if something is taking a long time for the client to evaluate.
A repeatable issue I see is that we can create a long-running property to evaluate “once a day” to reduce the client load, but then if someone uses that same property in action targeting or an action constraint, that long-running property relevance is copied to the Action, where it has to evaluate “Every Report”.