Why does my personal environment keep going to sleep?

Why does my personal environment keep going to sleep?

Question

It's my understanding that personal environments go to sleep because they are not being used, but I have a personal environment that is used every day. I have data to prove this, yet Outsystems keeps putting it to sleep every few weeks. What do I need to do to keep it awake?

08 May 2017

Suraj Borade

If you don't publish anything on your personal environment (I think it's 20 days), outsystems will push your personal environment to sleep. If you are just using app developed on it, OS considers that it's not used for development.

08 May 2017

2 replies

Last reply 05 Mar

Show thread

Hide thread

JohnGB

Champion

Suraj Borade wrote:

Hi Suraj,

If we just re-publish the current code that we have on the personal environment, does that count?

(just curious though as publish mean like having code changes or just re-publishing)

Cheers,

JohnB

28 Jun 2018

Matthew Vines

That's pretty poor design. Any idea if they will ever stop this practice?

05 Mar

Kristof Vandenbogaerde

I thought it was enough to just login in to your personal space to keep it awake. Do you really have to publish a new 'release' ?

16 May 2018

Kilian Hekhuis

mvp_badge

MVP

Hi Kristof,

Yes, you do. The reason behind this is that it's a developer environment. If you don't develop, it's considered not used. It's explicitly not meant as a user environment.

16 May 2018

Fábio Fantato

mvp_badge

MVP

Hi guys,

In fact, these is the rules to keep your env online:

Logs into platform via Service Center or Service Studio	+5 days
Wakes up environment	+10 days
Publishes an app/module	+10 days
End User(s) 7+ times in a week	+10 days

Web Service does not counts to keep env alive.

Cheers

Fabio Fantato

28 Jun 2018

3 replies

Last reply 20 Jul 2019

Show thread

Hide thread

JohnGB

Champion

Fábio Fantato wrote:

Hi guys,

In fact, these is the rules to keep your env online:

Logs into platform via Service Center or Service Studio	+5 days
Wakes up environment	+10 days
Publishes an app/module	+10 days
End User(s) 7+ times in a week	+10 days

Web Service does not counts to keep env alive.

Cheers

Fabio Fantato

Hi Fabio,

I get the other 3 on the list, however, a bit confused on the 4th. What does it mean?

Cheers,
JohnB

28 Jun 2018

Fábio Fantato

mvp_badge

MVP

John Guiller wrote:

Fábio Fantato wrote:

Hi guys,

In fact, these is the rules to keep your env online:

Logs into platform via Service Center or Service Studio	+5 days
Wakes up environment	+10 days
Publishes an app/module	+10 days
End User(s) 7+ times in a week	+10 days

Web Service does not counts to keep env alive.

Cheers

Fabio Fantato

Hi Fabio,

I get the other 3 on the list, however, a bit confused on the 4th. What does it mean?

Cheers,
JohnB

The 4th is regarding the end user access. i.e, the user that logs into your application (Users entity).

Should be a flow of access (logged features) more than 7 times in a week. It could be 7 different users doing login or one users doing login every day, for instance.

28 Jun 2018

Jan van Veldhuizen

Fábio Fantato wrote:

John Guiller wrote:

Fábio Fantato wrote:

Hi guys,

In fact, these is the rules to keep your env online:

Logs into platform via Service Center or Service Studio	+5 days
Wakes up environment	+10 days
Publishes an app/module	+10 days
End User(s) 7+ times in a week	+10 days

Web Service does not counts to keep env alive.

Cheers

Fabio Fantato

Hi Fabio,

I get the other 3 on the list, however, a bit confused on the 4th. What does it mean?

Cheers,
JohnB

The 4th is regarding the end user access. i.e, the user that logs into your application (Users entity).

Should be a flow of access (logged features) more than 7 times in a week. It could be 7 different users doing login or one users doing login every day, for instance.

I made a mobile app. So if I logout and login every day on my phone, then my environment would stay awake?
If yes, then that would be a process that can be automated.

20 Jul 2019

Kilian Hekhuis

mvp_badge

MVP

Hi Fábio,

Thanks for the info. Do you have a link to that info?

28 Jun 2018

2 replies

Last reply 19 Sep 2020

Show thread

Hide thread

Fábio Fantato

mvp_badge

MVP

Kilian Hekhuis wrote:

Hi Fábio,

Thanks for the info. Do you have a link to that info?

Hi Kilian,

There are a link to this , but it is an internal wiki. The info is public but the link is not.

Regards

Fabio

02 Jul 2018

Daniël Kuhlmann

mvp_badge

MVP

Fábio Fantato wrote:

Kilian Hekhuis wrote:

Hi Fábio,

Thanks for the info. Do you have a link to that info?

Hi Kilian,

There are a link to this , but it is an internal wiki. The info is public but the link is not.

Regards

Fabio

In the newly published page on What's an OutSystems personal environment the following is written:

Yes, completely free.

Your Personal Environment will be available:

As long as you continue developing your apps.
Your apps are consistently accessed by end-users.

If you stop developing in your Personal Environment for an extended period of time, your Personal Environment will be recycled. This allows saving resources for other developers. But don't worry! Long before that happens, we'll let you know. We'll send you emails remembering to continue developing in your Personal Environment.

If your environment ends up being recycled, we'll create a snapshot of the applications you had. We'll send you an email with instructions on how you can restore your apps in a new environment. Keep in mind that we only take a snapshot of the applications, not the data, and also, the snapshot will be available for the next 6 months.

19 Sep 2020

JohnGB

Champion

Hi guys,

I suddenly have come to think of it, what about if all the pages are set to be anonymous wherein it is just a for display web app and no logins required, what will happen to that environment?

In my initial thought, it will not be sufficient therefore the environment would still sleep, right?

Cheers,

JohnB

05 Jul 2018

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.

See the full guidelines