CAP Application not mocking remote services on every second app start

[#1]

Hello,

we are currently facing the issue accross multiple CAP projects, that during local development, mocking of remote services doesnt work as expected. 

Every second time our app restarts in local development during cds watch the remote mock services are not started.

We have observed that behavior during in multiple projects:
- It seems only to happen when trying to mock multiple remote services at the same time (3+)
- It seems to only occur in CAP node.js not Java
- It seems to be related to the cds.env not being populated properly.

We have first noted it down since cds 8.3.0

We can mitigate the problem by either causing the server to restart again or running the mocks on a different server seperatly, but a solution would be appreciated.

Best regards
Sören

[vobu]

very late to this party, but from my experience,  ~/.cds-services.json is the culprit in most cases.

So removing .bak-ing it might solve things™

$> mv ~/.cds-services.json ~/.cds-services.bak

[rbanania]

I'm developing locally using VSCode and my project doesn't even generate a .cds-services.json and I also have the same problem. Would you be able to point me somewhere else I can look or configure? The framework, documentation, and tutorials online have been pretty inconsistent.