ANTE User Manual

Schedulers

The Schedulers page lets you monitor the system's background scheduled tasks — the automated jobs that run on a timer (cron schedule). You can see each job's status, recent results, and execution history, and you can enable, disable, or manually trigger a job.

⚠️ Developer Access Only

The Schedulers page lives in the Developer panel, which requires developer privileges and a one-time password (OTP) sent to the team's Telegram channel. Developer panel access lasts one hour before you need to re-authenticate.

Note: This is a monitoring tool. Schedulers are defined in the system itself — you cannot create new schedulers or edit their cron timing from this page. You can only watch them and control whether they run.

Schedulers List

Navigate to DeveloperSchedulers.

The list shows every configured scheduler in a table with these columns:

ColumnDescription
NameThe scheduler's name, with its task type shown underneath
CronThe cron expression that controls when the job runs
StatusCurrent state — IDLE, RUNNING, or ERROR
Last ResultResult of the most recent run — SUCCESS, FAILED, or NONE (never run)
Last RunWhen the job last executed
DurationHow long the last run took
ActiveA check mark if the scheduler is enabled, otherwise a crossed-out circle

You can:

  • Search by Name or Task Type using the search box.
  • Sort by Name or Last Run.
  • Page through the list (20 per page by default).
  • Click any row to open that scheduler's detail page.

Scheduler Detail

Click a scheduler in the list to open its detail page. It is organized into three areas plus an actions bar.

Actions (top of page)

ButtonWhat it does
Enable / DisableTurns the scheduler on or off. The label flips depending on the current state. A disabled scheduler will not run on its schedule.
Run NowTriggers the job immediately, outside its normal schedule. Disabled while the job is already RUNNING.

Scheduler Information

FieldDescription
NameThe scheduler's name
Reference KeyThe internal key that identifies this scheduler
Cron ExpressionThe schedule that controls when it runs
Task TypeThe kind of task this scheduler performs
DescriptionA short description (if one is set)
ActiveWhether the scheduler is currently enabled

Status & Timing

FieldDescription
Current StatusIDLE, RUNNING, or ERROR
Last ResultSUCCESS, FAILED, or NONE
Last RunWhen it last executed
Next RunWhen it is scheduled to run next
Last DurationHow long the last run took
UpdatedWhen the scheduler record was last updated

Execution Stats (30 days)

A summary of the last 30 days of runs:

  • Total Executions — number of runs in the period
  • Success Rate — percentage of successful runs (shown in green at 90%+, amber at 70–89%, red below)
  • Failures — number of failed runs
  • Avg Duration — average run time

Execution History

Below the stats, a table lists each individual run, newest first:

ColumnDescription
StatusRUNNING, SUCCESS, or FAILED
Started AtWhen the run began
Completed AtWhen the run finished
DurationHow long it took
Output / ErrorThe job's output, or the error message if it failed (hover to see the full text)

Common Tasks

Viewing all schedulers

  1. Go to DeveloperSchedulers.
  2. Review each job's Status, Last Result, and Last Run.
  3. Use the search box (by Name or Task Type) to find a specific job.

Checking why a job failed

  1. Open the scheduler from the list.
  2. Check the Execution Stats for the failure count and success rate.
  3. Scroll to Execution History and find a run with FAILED status.
  4. Read the Output / Error column (hover for the full message).

Disabling a scheduler

  1. Open the scheduler's detail page.
  2. Click Disable.
  3. The job stops running on its schedule until you re-enable it.

Enabling a scheduler

  1. Open a disabled scheduler's detail page.
  2. Click Enable.
  3. The job resumes running on its normal schedule.

Running a job immediately

  1. Open the scheduler's detail page.
  2. Click Run Now (unavailable while the job is already running).
  3. The job runs right away; its history and stats refresh shortly after.

Tips

  • Watch the success rate — a falling success rate on the detail page is an early warning of a problem.
  • Read the error output — the Execution History captures the actual error message, which is the fastest clue to what went wrong.
  • Run Now doesn't change the schedule — a manual trigger runs once and does not affect the next scheduled run.