We often use XML data sources hosted by a local development server. When this server is not available (not started or not a developer machine), WindWard Designer takes an big amount of time to figurfe out the resource is not available. As a result, a document takes about 2 minutes per data source to open. Our documents often have 2 data sources making it 4 minutes, etc.

See video:
https://www.dropbox.com/s/q52y77v6yeh6eyk/4MinutesToOpenWindwardTemplate.mp4?dl=0

The attached document is the one used in the video, but it occurs with any document of which the datasource points to localhost while the server is not running.

I believe several enhancements are possible:
- take less time to discover whether or not the resource is available
possible make it a "timeout" setting so users can choose
- after the "would you like to edit" dialog, the whole resource accessing attempt restarts while it is already known to fail (it failed and I chose to edit the connection as I know it is wrong); avoid this second attempt to access the resource