Delay in "dispatch.yaml" update taking place

[Ben Guild]

I've noticed when deploying recently, the previous "dispatch.yaml" targets are cleared temporarily every time. This causes a completely different module/version to get called in the browser for that application for up to 10 seconds.

For us, they revert to the default module on the application.

Is this a permanent change?

[George (Cloud Platform Support)]

Hello Ben, 

More clarity is needed to isolate the actual issue in this case. You can use the dispatch.yaml to send incoming requests to a specific service (formerly known as modules) based on the path or host name in the URL. Specifying a certain version of that service in dispatch.yaml is not yet supported. You write "module/version". Do you mean module or version as well? 

It would help if you describe a step-by-step scenario enabling exact reproduce the issue exactly on our side. Sample code or any other instructions might prove relevant as well.