When Collect fails to connect ODK central and update forms of entities, the error message shown to the enumerator might be confusing and even stressing when it occurs multiple time.
Maybe the mention of a possible url setting (and the url) could be completed or replaced by an explanation of the most principal issues : no connection available right now or the draft has been deleted (published) .
And maybe this alert should be print to often when the connection problem does persist
As the manager of our Central instance, when i get this message on my phone, I can't wait to check that Central is ok 