Hi all,
When servoy cloud is down you can’t use your servoy developer 2026.3.1 anymore. Is there any way to bypass the login in case servoy login cloud is down?
From my developer.
From servoy cloud
Kind regards,
John Makkink
2 Likes
Servoy cloud is back online but the problem exist if it’s down you can’t use your developer anymore.
We’ve experienced the same issue a few times already.
If svyCloud is unavailable and you have to restart Servoy Developer, you’re no longer able to log in—which means you can’t work in Servoy at all.
It would be great if there were some kind of offline grace period or fallback mechanism for situations like this.
– Vik
4 Likes
Agreed, an offline grace period of 1 or 2 days would be good. So in case something happens we can continue using our developer.
It happened again for me today, this is a new thing and MUST be sorted!
As developers we can’t be held ransom to Servoy’s Cloud services not being available!
1 Like
Happened to 2 of our devs last week as well.
happening now, again!
This is really frustrating, can’t get my work done!
Can we get some clarifications about this?
Having talked to other developers in the german speaking area I found only some people noticed the downtime so it’s not common, and from personal experiments I found that without internet the developer seems to start. Since the npm build fails it doesn’t do me any good, but I digress.
Is this the planned behaviour, going forward, that the developer only runs as long as the Servoy Cloud can be accessed to check the licenses?
Does this apply only to the developer or also the server on startup, or does the server only saves some meta-data about running instances (I could ask why that does happen,. but it’s probably something to do with the management of on-preise servers from Servoy Cloud.
Hi Robert,
I did create a ticket for this: Jira
From what I understood the issues where coming from AWS changing things on their side.
Nevertheless, Johan mentioned in the ticket that a change could be made to catch the http statuscode.
As a workaround I was told to disconnect from network, launch Servoy and reconnect to network after Servoy launched. It’s a bit of a clunky workaround, but hopefully temporary.