Home / Product / Scheduled work

Let the product keep working

Run important product work at the right time—even when nobody is clicking.

Schedule the same actions your product uses on demand, and keep the person or system context they should run for.

See what it changes Technical guide ↗

Scheduled work in a product

Choose useful workSend a digest, synchronize data, process a queue

Set when it should happenOnce or on a recurring schedule

Run the known actionUse the same behavior and access context

Recurring work reuses product behavior

01Automate the calendarRun recurring work without a separate cron service.

02Avoid a second implementationSchedule the same named action used elsewhere.

03Preserve responsibilityMake the account behind scheduled work explicit.

Why it matters

Recurring work should not become a shadow version of your product.

A weekly report, storage synchronization, or pending-mail processor often starts as a script on someone's server. Over time it gains different access, different error handling, and different assumptions from the application.

Daptin schedules named actions that already belong to the product. Each task records what to run, when to run it, the input it needs, and the account whose context applies.

Schedules return after restart because the task definition is stored. The team can understand recurring work as part of the backend rather than as invisible machine configuration.

Turn routine work into product behavior

Make digests, cleanups, syncs, and queue processing explicit.

Keep on-demand and scheduled paths aligned

Improve the action once for both ways of starting it.

Know whose access applies

Run for a selected account instead of defaulting to ambient administrator power.

How it fits

Part of one connected backend.

Scheduled work does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Define

Create the action that represents the work.

Step 2Schedule

Choose its timing, input, and acting account.

Step 3Run

The scheduler invokes the ordinary action path.

Step 4Persist

Stored task definitions can be loaded again after restart.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Customer digest

Send a weekly summary built from current account data.

Provider sync

Refresh connected records every hour for an authorized user.

Queue processing

Work through pending outbound messages or storage changes.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes scheduled work more useful.

Know the boundary

What Daptin leaves in your hands.

Scheduling does not guarantee that outside work happens exactly once. Plan idempotency, time zones, overlapping runs, provider limits, failure alerting, and recovery for every consequential task.

Understand the operating responsibility →

Build from one foundation

Make scheduled work part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities