Features · Scheduler

Scheduler

Updated 2026-05-25 Feature eCommerce Insights team

The Scheduler drives every recurring task in eCommerce Insights: PDP audits, Prompt Runs sessions, alert checks, and review re-pulls. Configure cadence per task (daily, weekly, monthly, custom cron). For users who run their own infrastructure, there is a /?api=cron_tick heartbeat endpoint.

Recurring audits with timezone-aware send windows.
Recurring audits with timezone-aware send windows.

What it does

The Scheduler is the heartbeat. Every recurring task in eCommerce Insights is registered with the scheduler and runs on its configured cadence.

Available cadences

Hourly
Useful for review re-pulls when the underlying source supports an API.
Daily
Useful for Agent Lens spot checks against a small set of canonical URLs.
Weekly
Default for PDP audits and Prompt Runs sessions. Balances signal freshness against cost.
Monthly
Useful for Persona re-clustering and brand-wide Sentiment rollups, both of which produce noisy drift if run more often.
Custom cron
A standard 5-field cron expression. Validated on save.

Per-task scheduling

Each registered task has its own cadence. Workspace-level defaults can be overridden per task. The most-used overrides:

Run history

The Schedule page exposes the last 100 runs per task with status, duration, error message (if any), and a one-click "view detail" link. Useful for diagnosing why a Prompt Runs session took 4x its usual time or why a PDP audit batch failed mid-run.

Cron-as-a-service heartbeat

Endpoint: GET /?api=cron_tick. Hitting this URL advances every task that is due.

# Every 5 minutes from your own cron host
*/5 * * * * curl -s "https://app.ecommerceinsights.ai/?api=cron_tick&workspace=YOUR_WORKSPACE_ID&token=YOUR_TOKEN" > /dev/null

Or from Render Cron / Vercel Cron / GitHub Actions:

# GitHub Actions
on:
  schedule:
    - cron: "*/5 * * * *"
jobs:
  tick:
    runs-on: ubuntu-latest
    steps:
      - run: curl -fsSL "https://app.ecommerceinsights.ai/?api=cron_tick&workspace=${{ secrets.SHELFSCOPE_WS }}&token=${{ secrets.SHELFSCOPE_TOKEN }}"

Calls to the heartbeat are idempotent. Hitting it twice in the same minute is harmless — tasks only advance when they are due.

When to use Use the heartbeat when you want predictable schedule timing under your own observability. Use the built-in scheduler (no extra setup) for everything else.

Manual "Run now"

Every task has a per-task "Run now" button on the Schedule page. There is also a workspace-level "Run scheduler now" button that triggers every due task in one shot.

Common questions

What's the default cadence?
Weekly for PDP audits and Prompt Runs sessions, hourly for review re-pulls (where API is available), and daily for Agent Lens spot checks. All overridable.
What does the heartbeat endpoint do?
Hitting /?api=cron_tick from any external scheduler (a cron job, Render Cron, Vercel Cron, GitHub Actions, etc.) advances every scheduler task that is due. We provide this for users who prefer to drive the schedule from their own infrastructure rather than rely on eCommerce Insights's.
Will tasks queue if I hit the heartbeat twice in a minute?
No — task completion is checkpointed. Hitting the heartbeat more often is harmless; tasks only advance when they're due.
What happens if a scheduled task fails?
It is retried with backoff (immediate, 5 min, 30 min, 2 hr, 12 hr, then daily). After three failures the task is flagged and an alert fires.

Ask AI about this page

Open this topic directly in your favourite AI assistant — the prompt is prefilled.

Was this page helpful?
Thanks — recorded.

Try this yourself

See eCommerce Insights on your own catalog. The free trial covers your full SKU set across five AI engines.

Start free trial
LLM-friendly summary of this page
Scheduler drives recurring tasks in eCommerce Insights: PDP audits (weekly default), Prompt Runs sessions (weekly default), alert checks (run after each PDP audit and Prompt Runs session), review re-pulls (hourly via API where available; on upload otherwise), Agent Lens spot checks (daily default). Per-task cadence override: daily, weekly, monthly, or custom cron expression. Run history view shows last 100 runs per task with status, duration, and any errors. Cron heartbeat at /?api=cron_tick advances every scheduler task that is due; safe to hit repeatedly. Designed for users who prefer to drive the schedule from external infrastructure (Render Cron, Vercel Cron, GitHub Actions). Manual 'Run scheduler now' button on Schedule page triggers all due tasks immediately. Failure retry: immediate, 5 min, 30 min, 2 hr, 12 hr, daily; after three failures task is flagged and alert fires.