By submit or upload application due you mean submitting a case or upload some document or working on case  ? 

I believe what Veera is asking is, if you were to complete an entire flow and resolve a case [potentially] offline, and then you go to sync the case to "submit the application" what is the minimum network strength required.

I feel as though Pega does not have any set/defined minimums and this question may be more of a low level networking/OS sort of question. But I could be wrong, and will need Mobile SMEs to weigh in here.

I imagine we might fall under the philosophy that this question is somewhat N/A in the sense that offline mobility is supposed to handle this. Even with poor or spotty connections, the inherent design is to ensure no data loss and complete the sync once [better] networking connectivity is restored.

But that is just my read on the question and how the product is designed.

Hi Veera,

We can only ever know what the network connectivity *was*, but never truly what it *is*.  A network connection can fail one second and succeed the next and vice versa.  There is JavaScript API for testing the network status.  A code example can be found here: https://community.pega.com/sites/default/files/mobileclient/7312/api/client_api/container_example_network_status.html.

That will give you the best indicator of what the network status is, but requires custom JS.  Let us know your use case and we might be able to give better recommendations around how to proceed.

- James

I also want to add that our offline syncing takes care of any network issues.  If the sync fails because of any network issue, the syncing is simply paused and then resumes when it is able to.