Tally automations and Activity

Tally automations are scheduled or condition-based routines that look for work and create supervised jobs. Activity is the screen where users see what ran, what is waiting, what failed, and what needs a decision.

LedgerHQ no longer runs a built-in daily proposal or morning queue. The full-page Tally chat opens blank and ready. Scheduled Tally work should come from automations or standing instructions the firm intentionally creates. Use Activity when the user wants to inspect work history or the current supervision queue.

What Activity Shows

Activity groups the practical supervision signals:

• work Tally completed today;
• jobs waiting on approval or more information;
• automation cards and their current state;
• recent run history;
• failed runs that can be retried;
• paused automations;
• company-level blockers that need attention.

The top-line counts should reflect real work for the selected day. Old proposal records should not appear as current work. If a date has no activity, the page should say so plainly instead of implying that hidden work ran.

Automation Cards

Automation cards show whether a routine is active, paused, or needs attention. Supported controls include pausing, resuming, retrying, and running now where the automation allows it.

Use Run now when a firm wants Tally to check a supported workflow without waiting for the next scheduled scan. Use Retry when a previous run failed and the user believes the blocking condition is fixed. Use Pause when a company or duty should be manually supervised for a while.

Common Automations

Current Tally automations can support daily bookkeeping review, stale bank-feed checks, uncoded transaction review, missing statement checks, client blocker summaries, reconciliation readiness, close preparation, and custom instructions the firm defines. Some automation names may come from older storage keys, but visible copy should describe the current user-facing workflow.

Automations do not bypass Tally's duties or approval model. They create or run work within the contract. If the relevant duty is off, the automation should not generate active work for that duty. If a company is paused, scheduled scans should skip it.

Waiting On You

Waiting-on-you items are the most important part of Activity. They mean Tally cannot safely continue without a human decision, missing document, approval, or clarification.

Examples include:

• a prepared reconciliation worksheet that needs approval;
• a close checklist with red items;
• a missing statement period that needs a request or waiver;
• a client request that needs review;
• a failed automation that needs retry after a configuration fix;
• a prepared report delivery that needs confirmation.

Reading Run History

Run history explains what Tally attempted and what happened. It is useful when the user asks "Did Tally already work on this?" or "Why did this not happen?"

If the run history says nothing happened, that can be a correct result. For example, a missing-statement automation may find no due gaps, or a coding automation may skip rows that are still pending at the bank. The right question is not only whether the automation ran, but whether the source conditions required action.

Troubleshooting Activity

If Activity looks wrong, check these first:

1. Is the correct date selected?
2. Is the company paused in the Tally contract?
3. Is the relevant duty off?
4. Is the item still pending, unverified, or blocked by warnings?
5. Did a run fail and need retry?
6. Is the work visible in another workflow, such as Fast Coding, Statements, Bank Recs, or Month-End Close?

If the answer is still unclear, create a support ticket from Tally and include the company, date, automation name, and what the user expected to happen.