Sync Visibility
This page reflects the latest logs stored in Supabase. Missing, partial, or incomplete logs mean coverage is unverified, not necessarily offline.
Using legacy `scrape_log` compatibility because the source-level `sync_logs` table is not present in the current production schema.
Legacy sync activity recorded
Recent overall scrape history exists, but source-level coverage is still unverified on this database schema.
Missing, partial, or incomplete logs are treated as unknown coverage rather than offline status.
Source Coverage (24h)
NEVDIS (Vehicle)
No logs yetNo sync log has been recorded for this source, so freshness is unknown.
Stored recall data exists for this source, but freshness is unverified until a completed sync log is recorded.
Last completed sync
Not yet available
New Records
Not yet available
Latest Stored Recall
REC-006589 · 20 Apr 2026
ACCC (Product)
No logs yetNo sync log has been recorded for this source, so freshness is unknown.
Stored recall data exists for this source, but freshness is unverified until a completed sync log is recorded.
Last completed sync
Not yet available
New Records
Not yet available
Latest Stored Recall
PSA-qv564c · 22 Apr 2026
FSANZ (Food)
No logs yetNo sync log has been recorded for this source, so freshness is unknown.
Stored recall data exists for this source, but freshness is unverified until a completed sync log is recorded.
Last completed sync
Not yet available
New Records
Not yet available
Latest Stored Recall
FSANZ-rhpkk6 · 21 Apr 2026
TGA (Medicine)
No logs yetNo sync log has been recorded for this source, so freshness is unknown.
Stored recall data exists for this source, but freshness is unverified until a completed sync log is recorded.
Last completed sync
Not yet available
New Records
Not yet available
Latest Stored Recall
TGA-558493 · 15 Apr 2026
Recent Sync History
| Status | Source | Date / Time | Duration | New Records |
|---|---|---|---|---|
SUCCESS | OVERALL | 22 Apr, 08:20 pm | 8.0s | +1 |
SUCCESS | OVERALL | 22 Apr, 08:00 pm | 2.8s | 0 |
SUCCESS | OVERALL | 22 Apr, 05:37 pm | 2.5s | 0 |
SUCCESS | OVERALL | 22 Apr, 05:37 pm | 3.6s | 0 |
What this page can prove
RecallAU stores both sync logs and recall records. A completed success log is the only thing treated as verified freshness. Stored recall dates are shown as evidence of what is currently in the database, but they do not replace missing or partial logs.