Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.anyshift.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

A custom report is a reusable template for the kind of output you want Annie to produce on demand or on a recurring schedule. You author the template once (a runbook plus the block layout), and Annie generates a fresh report instance every time it runs. Open Reports → Custom in the app to see your existing definitions and instances.

​
Generating a report

Two ways to fire a report:
  • Generate now on the definition page runs Annie immediately and adds a new instance to the list.
  • A scheduled definition fires automatically on the cadence you configure (see below).
While an instance is generating, you can Cancel it from the instance detail page. If a generation fails, the instance shows a card with Retry (re-runs and replaces the failed instance) and Delete (removes the failed instance from the list, keeps the definition).

​
Scheduling

A definition’s schedule controls when it runs automatically. Open Settings → Edit schedule on the definition page. The picker offers six cadences:
CadenceConfigures
Manual onlyNo automatic runs. Only fires when you click Generate now or trigger via API.
DailyEvery N days at HH:MM UTC (1 to 30 days).
WeeklyEvery 1, 2, or 3 weeks on a chosen weekday at HH:MM UTC.
MonthlyThe first, second, third, or fourth chosen weekday of every N months at HH:MM UTC.
YearlyA fixed month and day at HH:MM UTC.
Custom cron expressionA 5-field cron string for cadences the picker doesn’t model.
The picker shows the next 3 fire times below the form so you can confirm the schedule before saving. The definition page list also shows a “Next run in X” hint next to scheduled definitions.

​
Constraints

  • All schedules are evaluated in UTC. Pick the time accordingly: 14:00 UTC is 7:00 PT, 10:00 ET, 16:00 CET (winter).
  • The minimum cadence is daily. Sub-daily schedules are rejected at save time.
  • Weekly caps at every 3 weeks. For longer recurring cadences, switch to Monthly.

​
Examples

RecurrenceCadence
Daily at 14:00Every day at 14:00 UTC.
Every 3 days at 09:30Fires every 3 days, exact wall-clock gap.
Every 2 weeks on Monday at 14:00True biweekly: every 14 days.
First Monday of every month at 14:00One fire per month, always the first Monday.
Third Friday of every quarter at 09:00One fire per quarter.

​
MCP

The save_report_definition tool also accepts a schedule argument when persisting a report definition from a chat. Pass "manual", a 5-field cron expression, or one of the prefix forms (every-Nu:<cron>, nth-N:<cron>) to schedule the definition at creation time. The tool description spells out the accepted shapes with worked examples.

​
Visibility of past runs

Each definition keeps a list of instance runs (most recent first). Successful runs link to the rendered report; failed and cancelled ones stay visible for history with their status badge. Superusers can toggle Show deleted in the definition page header to bring soft-deleted instances back into the list.