Search pipeline
Knack -> Algolia
Source
Knack
Execution
Vercel cron route
Destination
Algolia index
- Knack records
- Unavailable
- Algolia records
- Unavailable
- Last index sync
- No recorded sync yet
- Unavailable
- Records scanned
- Unavailable
LoadingShareable monitorVercel replacing cc-algolia
CineConcerts sync health, status, and pipeline context
This service replaces the old Heroku sync worker. It keeps event search current by moving Knack data into Algolia, keeps inventory mirrored from Amplifier into Notion, and exposes machine and human monitoring surfaces so the state of the pipeline is obvious at a glance.
Pipeline topology
What this service is actually doing
Loading
Inventory pipeline
Amplifier -> Notion
Source
Amplifier
Execution
Vercel cron route
Destination
Notion database
- Notion connectivity
- Loading
- Live connectivity check from the API route.
- Trigger cadence
- Hourly
- Controlled by Vercel cron, not a resident worker dyno.
- Operational note
- This page verifies Notion access directly. The actual inventory write path runs in the protected cron endpoint, which is intentionally not exposed in the UI.
Dependency checks
Health of each external leg
Monitoring surfaces
Which URL each audience should use
Primary status page
/monitor
Human-readable status console with pipeline context and raw payload visibility.
Machine health
/health
Drop-in replacement for the old cc-algolia Heroku health endpoint.
API health
/api/health
Structured JSON payload for monitors, dashboards, and integrations.
Events API
/api/events
GeoJSON event surface exposed by this app for downstream tooling.
Operational runbook
How to interpret red or yellow states
If record alignment drifts
Compare Knack and Algolia counts here first. If the delta grows, inspect the Knack to Algolia cron route and the latest production deployment on Vercel.
If Notion goes red
That usually means the token lost access or the target database changed. Check the Notion integration sharing and the configured database ID.
If the monitor itself fails
Use the raw payload below, then check Vercel deployment logs. This app is serverless, so there is no long-lived worker process to inspect.
Service readiness
Configuration and exposure
Events API surfaceMissing config
Knack to Algolia syncMissing config
Amplifier to Notion syncMissing config
Environment readiness
Credential presence by dependency
Knack credentials
Missing
Algolia credentials
Missing
Amplifier credentials
Missing
Notion credentials
Missing
Schedule notes
How this service runs on Vercel
Execution model
Unavailable
Cron schedule
Unavailable
Protected operations
Manual trigger routes still exist, but this dashboard is intentionally read-only so monitoring does not depend on entering secrets into the browser.
Raw payload
Exact JSON returned by /api/health
Waiting for live health response...