Abrova
☰ Docs menu · Scheduling
Coming soon. Abrova Flags is coming soon. This page describes how it will work; it can’t be used yet.

Flag Scheduling

Schedule flags to automatically enable or disable at a specific date and time — perfect for product launches, promotions, maintenance windows, and time-sensitive features.

Last updated: 27 Oct 2026
Flag Scheduling.

Schedule flags to automatically enable or disable at a specific date and time. Perfect for product launches, promotions, maintenance windows, and time-sensitive features.

How Scheduling Works#

From the dashboard, you can schedule a flag to change state at a future time. Abrova Flags checks for due schedules every minute and applies them automatically.

Schedule Enable

Set a flag to automatically turn ON at a specific date/time. Great for launches and feature reveals.

Schedule Disable

Set a flag to automatically turn OFF at a specific date/time. Useful for promotions and temporary features.

Use Cases#

Product Launches

Schedule a feature to go live at midnight on launch day — no manual intervention needed

Limited-Time Promotions

Enable a promo banner at 9 AM and disable it at midnight automatically

Maintenance Windows

Schedule a maintenance mode flag to enable during planned downtime

Seasonal Features

Enable holiday-themed UI changes during specific date ranges

Managing Schedules#

Schedules are managed from the Feature Flags page in Abrova Console:

  • Create: Create or edit a flag → in the Schedule field pick "Enable at" or "Disable at" and set the date and time
  • Cancel: Open the flag detail page → click "Cancel Schedule" to remove a pending schedule
  • View: Scheduled flags show a clock icon and the scheduled time in the flag list

When Your App Sees the Change#

A schedule changes the flag in Abrova Flags. Your code needs no change, but each SDK picks up the new state at its next refresh:

Server SDKs (Node.js, Next.js server)

Within about 30 seconds, at the next automatic rule refresh

Client SDKs (Flutter, React Native, Android, iOS, Next.js client)

At the next fetch: app start, a change of user or attributes, a return to the foreground after 15 minutes, or refresh()

If a client must switch close to the scheduled time, call refresh() at that moment or set refreshIntervalSeconds (minimum 60). Each client fetch counts as one evaluation.

Note.

Schedules are checked every minute. There may be up to a 60-second delay between the scheduled time and the actual state change.

Was this page helpful?
Report a problem