Historical Tally automation activity
Custom Tally automations have been retired. Use Activity to review historical runs and continue using LedgerHQ's built-in bookkeeping workflows.
Custom schedules are retired
LedgerHQ retired the general-purpose custom Tally Automations feature. New
custom schedules and event-driven automations cannot be created, revised, run,
or continued. The old /tally/automations link remains a compatibility
redirect to /tally so saved links do not break.
This retirement does not change LedgerHQ's built-in bookkeeping workflows. Bank-feed rules and AI posting, statement coverage and OCR, reconciliation, scheduled journal entries, depreciation, loan schedules, revenue recognition, recurring invoices, reminders, report schedules, Work Summary, Payroll Report Review and QuickBooks import continue through their own supported surfaces. Bank CSV import is available in Settings > Import & Export. Ordinary Tally chat and existing Tally Connections remain available.
Reading historical activity
Older custom automation runs may still appear in Tally > Settings > Activity and in support or audit views. They are historical records, not work that will run again. A historical row may include its original title, trigger, status, outcome, error, linked job, sanitized receipts, and the date it ran.
The Activity history can show this note:
Historical custom automation runs may appear here. Custom schedules no longer run.
Queued, running, or needs-input runs were cancelled during retirement with the
reason Custom Tally automations were retired by LedgerHQ. Their source event
and payload remain available for audit. Secrets and raw provider payloads are
not exposed.
What to use now
Ask Tally in ordinary chat about a current bookkeeping task, or open the relevant first-class workflow in LedgerHQ. For example, upload a statement and use Bank Recs, review a company's Work Summary, run Payroll Report Review, or start a supported import from Import & Export. These workflows own their evidence, scope, accounting rules, and activity history directly.
If a historical run needs explanation, include the company, run date, and the visible outcome when you create a support ticket.