Scheduled Operations

Scheduled operations allow you to automate recurring tasks on Cloud VPS and other services managed through the SeFlow panel. You can schedule actions such as power on/off, reboots, snapshots, or maintenance activities by defining frequency, timing, and the resources involved.

Tip: Use scheduled operations to reduce repetitive manual tasks, optimize operational costs, and keep your environments predictable and easier to manage.

What Scheduled Operations Are

A scheduled operation is a rule configured within the SeFlow panel and consists of:

  • Action to perform (e.g., power off VPS, power on VPS, create snapshot);
  • Resource on which the action is applied (specific Cloud VPS);
  • Frequency (once, daily, weekly, monthly);
  • Exact execution time;
  • Status (enabled/disabled).

All operations are executed by the SeFlow platform, regardless of the operating system state of the VPS.

Tip: Think of scheduled operations as a “platform-level cron”: they work even if the VPS is unreachable, as long as the resource exists and is managed in the panel.

Where to Find and Manage Scheduled Operations

You can access the dedicated section via the SeFlow panel:

  • Utilities → Scheduled Operations

From this interface you can:

  • view all existing scheduled operations;
  • filter them by type, status, or resource;
  • create new scheduled operations;
  • edit existing operations;
  • enable or disable operations;
  • delete operations that are no longer needed.
Tip: Use clear naming conventions (e.g., “Shutdown_Test_23:00”) to easily identify schedules in multi-server projects.

Types of Available Scheduled Operations

  • Automatic power on of a Cloud VPS;
  • Automatic power off of a Cloud VPS;
  • Scheduled reboot;
  • Automatic snapshot creation before critical activities;
  • Other maintenance actions supported by the platform.
Tip: Avoid timing conflicts (e.g., snapshot creation and VPS shutdown at the same minute). Always leave at least 5 minutes between different operations on the same resource.

Create a New Scheduled Operation

To add a new scheduled operation:

  1. Log in to the SeFlow Panel.
  2. Navigate to Utilities → Scheduled Operations.
  3. Click Add Scheduled Operation.
  4. Fill in the required fields:
    • Name of the operation;
    • Description (purpose, context, notes);
    • Action to perform (e.g., power on, power off, snapshot);
    • Resource to manage (select the Cloud VPS);
    • Time and frequency.
  5. Confirm creation.
Tip: After creation, make sure the operation appears as “Enabled” and check the date of the next expected execution.

Configuring Schedule Time

You can configure different schedule types:

  • One-time execution – for tasks with a specific date/time;
  • Daily – recurring every day;
  • Weekly – executed on selected weekdays;
  • Monthly – executed on specific days of the month.

You can also define:

  • Start date of the schedule;
  • Exact execution time;
  • End date (optional).
Tip: Schedule sensitive operations (snapshots, shutdowns) during low-activity periods to reduce impact on users.

Managing Existing Scheduled Operations

On the scheduled operations management page you can perform several actions:

Editing an Operation

You can modify:

  • operation name;
  • description;
  • frequency and time;
  • associated resource;
  • operation type.

Activation and Deactivation

Using the dedicated toggle, you can:

  • temporarily disable a scheduled operation without deleting it;
  • re-enable it at any time.
Tip: Prefer disabling instead of deleting if you are unsure whether the operation might be needed again.

Deleting an Operation

You can permanently remove a scheduled operation when it is no longer required.

Monitoring Scheduled Operations

For each scheduled operation, you can review:

  • Last execution – date, time, and status;
  • Next execution – based on the configured frequency;
  • Error logs – useful for diagnosing issues (e.g., VPS unreachable, resource unavailable).
Tip: Periodically review the status of critical scheduled operations (snapshots, shutdowns) to ensure that they are executed correctly.

Use Cases: Practical Examples

Nightly Shutdown of Test Environments

Automatically shut down Cloud VPS used for testing every night (e.g., 23:00) to reduce unnecessary resource usage.

Tip: Combine nightly shutdowns with automatic morning power-on (e.g., 08:00) to keep servers ready for your team.

Weekly Reboot of Critical Applications

Useful for freeing resources, applying updates, and improving service stability.

Snapshot Before Maintenance

Schedule automatic snapshots a few minutes before planned updates to enable quick rollback.

Multi-Time-Zone Management

Create different schedules for teams operating in different time zones.

Best Practices

  • use clear and descriptive names;
  • avoid overlapping actions on the same VPS;
  • test new schedules on non-production environments;
  • combine snapshots and backups for maximum safety;
  • document critical schedules internally.
Tip: Before applying scheduled operations to production environments, always assess user impact and communicate maintenance windows when necessary.
Was this answer helpful? 0 Users Found This Useful (0 Votes)