Some of what Finocket does for you takes longer than a tap. A Tally sync reads a year of vouchers, an opening-balance import waits for you to confirm a plan, an outreach agent proposes a month of messages and sits there until somebody says yes, and a scheduled report goes out at six in the morning whether or not you are awake.
Running jobs is the one screen that answers “is anything happening?” for all of them at once.
Open Running jobsWhat is in flight, what is waiting on you, what stopped badlyHow to reach it
- On a tablet or a computer, it is the checklist icon in the system dock down the left edge of every screen — the Work group, between the bell and your activity history.
- On a phone there is no dock, so open Activity and tap Running now at the top.
- Search works too: press the search icon and type “running” or “jobs”.
The four groups, in the order they matter
Jobs are not listed by time. They are listed by what they need from you, so the top of the screen is always the part that is still live.
- Running now — Finocket is working on these. You do not need to keep the screen open; closing the tab does not cancel anything. This group is shown even when it is empty, because “nothing is running” is an answer and blank space is not.
- Waiting for you — these stopped on purpose. An import that has parsed your data and wants a confirmation before it writes anything, or an outreach plan nobody has approved. They will wait indefinitely. Nothing in this group has touched your books.
- Did not finish — these stopped badly. Open the job and the screen it belongs to shows the failure in the words the other system used, not a code.
- Finished recently — the last few that completed, newest first, so you can confirm last night's report actually went.
What counts as a job
Five kinds of work, each linking through to its own screen:
- Tally sync — bringing vouchers and masters in from TallyPrime, or sending them back. Opens Tally → Runs, where the full step-by-step and the rollback live.
- Tally import — the one-time opening-balances migration. Opens the import screen, where a parsed plan waits for your confirmation.
- Growth agent — an outreach plan an agent drafted, with how many people it would contact and how many consent would block. Nothing sends until you approve it.
- Scheduled report — a report that goes out on a cadence you set.
- Automation — one of your own rules firing when the event it watches for happened.
Scheduled reports and rules are the honest exception
Two of the five record only outcomes. A scheduled report and an automation rule are both over in a moment from your point of view, so neither ever appears under Running now — they show up in Finished recently or, if the send failed, under Did not finish. They are on this screen anyway, because “nothing is running, and last night's digest went out at 6:02” is the answer you came for.
When a job says “Not recognised”
Occasionally a job carries a status this version of the app has not been taught to read — usually because the part of Finocket that runs it was updated a little ahead of the part that displays it. When that happens the screen says so plainly and prints the raw status, rather than filing it under “finished”.
That is deliberate. Guessing would mean telling you an import succeeded when nobody knows whether it did. Open the job — the screen it belongs to always understands its own statuses.
Refreshing
- While anything is running or waiting, the screen re-reads itself every twenty seconds on its own.
- Once nothing is in flight it stops, so an idle tab left open overnight is not quietly querying all night. Use the refresh control at the top when you want a fresh read anyway.
- If a stream cannot be read — a dropped connection, most often — the screen names it in a banner instead of showing you a shorter list. A shorter list looks exactly like “nothing is running”, and that is the one wrong answer this screen must never give.