Managing routines

Everything running on a schedule is at app.ginicomputer.com → Routines: what it does, when it next runs, who owns it, and every run it has done.

You can also manage a routine from the channel: "@Gini pause the Monday report" works.

Editing what it does

Open the routine and edit its instructions in plain English, the same way you wrote them. Changes apply from the next run.

Common edits, and how to phrase them:

• Narrow it: "only EMEA", "exclude internal accounts"
• Change the output: "as a table", "lead with the number that moved most"
• Add a source: "include the Stripe figures"
• Add a condition: "if churn is above 4%, say so at the top and tag @sam"

Pausing and resuming

Pause a routine when the work is on hold: a quiet period, a team change, a tool being migrated. It stops running and keeps its history and settings.

Pause rather than delete unless you're sure. Deleting loses the instructions, and rewriting them from memory is how a good routine comes back slightly worse.

Reading the history

Each routine keeps its runs: what it did each time, what it posted, where it stopped, what it cost.

Two things this is good for.

A routine that stopped being useful. Read the last four runs together. Usually one of them is where the output drifted, and there's an obvious cause: a source changed, a team reorganised, the question stopped mattering.

A routine that costs more than you thought. The history shows the credits per run. A job that grew from 200 credits to 600 is doing more work than it used to, which is worth understanding rather than just paying for.

Moving where it posts

Change the channel on the routine. Gini has to be in the destination channel: invite it first with /invite @Gini.

Ownership

A routine runs with its owner's access to connected tools. If the owner leaves the company or disconnects a tool the routine depends on, the routine stops and says so rather than running with less data and looking fine.

Before someone leaves, reassign their routines. People and permissions covers offboarding properly.

When a routine fails

It posts what happened, in its channel, at the time it was meant to run. It doesn't fail silently and it doesn't skip quietly.

An expired connection is by far the most common cause. See Fixing a broken connection. A routine whose approval nobody clicked will have stopped and said so.

Deleting one

From the routine, or "@Gini delete the Monday report". The schedule stops immediately. The history stays until your retention window expires, so you can still see what it did.