Background Jobs & Scheduled Tasks

Background Jobs Overview

1 What Runs Automatically

AeroTrack performs several automated background tasks to keep compliance data current and alert users to upcoming deadlines:

Job	Frequency	What It Does
AD/SB URL Check	On demand / scheduled	Fetches monitored AD/SB source URLs and detects content changes.
Inspection Due Calc	On flight log approval	Recalculates next-due values for all inspections when aircraft hours/cycles update.
Audit Logging	On every mutation	Records create/update/delete actions with before/after snapshots.
Session Cleanup	On login	Validates active sessions and enforces single-device login per user.

Unlike traditional cron jobs that run on a fixed schedule, most AeroTrack background tasks are event-driven — they execute in response to user actions (flight log approval, data save, etc.) for immediate consistency.

AD/SB URL Monitoring

2 How It Works

When an AD or SB record has Monitoring Enabled and a Source URL pointing to a DGCA, FAA, or EASA web page, the system can check that URL for changes.

The check compares a hash of the current page content with the previously stored hash. If the content has changed, a notification is created with the appropriate severity (CRITICAL or WARNING).

Set up monitoring for all active ADs to stay ahead of revision changes. See AD/SB Monitoring for setup instructions.

3 Run a Manual Check

Navigate to Tech Library → AD/SB → Notifications (/tech-library/ad-sb/notifications) and click the Run Check button to trigger an immediate URL monitoring scan across all monitored AD/SB items.

AD/SB Notifications page with Run Check button to trigger manual URL monitoring scan

The check runs in the background and creates notification records for any detected changes. Refresh the page to see new results.

The Run Check button fetches external URLs. Ensure the server has internet access and the source URLs are reachable. Failed checks are logged but do not create false-positive notifications.

Due Calculations & Auditing

4 Inspection Due Engine

The inspection due calculation engine runs automatically whenever:

Trigger	Effect
Flight log approved	Updates aircraft total hours/cycles, then recalculates remaining margins for all inspections on that aircraft.
Inspection marked done	Updates the last-done baseline and recalculates the next-due values.
Inspection created/edited	Calculates initial next-due values based on intervals and baseline.

Results are visible on the Inspection Schedule matrix and the Inspection Due Report.

Audit Log showing automated calculation events with timestamps and user attribution

5 Audit Trail

Every automated action is logged in the Audit Log at /settings/audit-log. The log records:

Field	Description
Entity	Which table/record was affected.
Action	Create, Update, or Delete.
User	Who triggered the action (or “System” for automated tasks).
Timestamp	Exact time of the action.
Before / After	JSON snapshot of the data before and after the change.

Use the Audit Log filters (entity type, action, date range, search) to investigate specific automated events or verify that background processes are running correctly.