RumataIdle hibernation
Understand what goes to sleep, how it wakes up, and where to change the timer.
Step-by-step guidance.
When an activity is idle
An activity deployment can sleep between calls. In its deployment settings, choose Idle before sleeping, then select Deploy activity. The first workflow call after sleep waits for the activity to wake. As the dialog warns, this can take up to 90 seconds. Activity deployment settings.
When the building workspace goes idle
The development machine runs your chat tools, preview, and code editor. It can pause after inactivity. On your next visit, let it start or resume before using the preview. A paused development machine does not by itself take your published frontend offline.
Open Factory Settings to review workspace persistence and the available idle controls. Save important work before stopping a machine. Machine settings and shutdown behavior.
When the database goes idle
The database has a separate sleep timer. It wakes on the next connection, so the first request after a quiet period may take longer. Database activity resets the timer.
Change the database sleep timer
Open System Explorer → Database → Operations → Idle hibernation. Choose a preset or enter Days, Hours, and Minutes within the displayed limits. Review the total, then select Save sleep timer. Cancel leaves it unchanged.
The same control is available in the extended Overview. The policy applies to the entire billing account, not just the screen you opened. Sleep timer controls · Quotas.
Technical reference
Timer scope
Changing the database sleep timer updates the billing account’s database.ready.seconds policy. Development-machine shutdown and workspace persistence are separate. Database operations has the exact controls.