Housekeeping
Housekeeping is where you check on the work Jelly does by itself, in the background. Look here when something that should have happened on time hasn't: a snoozed conversation that didn't come back, a scheduled message that didn't go, or mail that's slow to arrive.
The page also has a few switches that belong to your Jelly as a whole: usage reporting, Google sign-in, and, for a self-hosted Jelly, the connection to Jelly's services.
To open it, choose Team settings in the account menu, then Housekeeping. Only Admins and the Owner can see it.
The sweep
Everything Jelly does on a clock is done by one background job, called the sweep. Each time it runs, it:
- sends messages scheduled to go later;
- wakes snoozed conversations whose time has come;
- fetches new mail from IMAP accounts and Gmail accounts;
- tries again with incoming mail that failed, and with webhooks that couldn't be delivered;
- ends sign-ins that have expired;
- checks the team's billing, and sends billing emails;
- sends the day's usage report, if it's due.
The sweep runs on a regular schedule, and also at the moment something is due, such as a snooze ending. It runs every five minutes as well while the team has an IMAP account, or a Gmail account that Jelly has to check for itself (one without pushes from Gmail). That's why mail from those accounts can take up to five minutes to appear.
Housekeeping says when the sweep last ran. If you're waiting for something, press Run the sweep now to run it straight away.
Manager connection
A self-hosted Jelly can connect to Jelly's services here, to get support and the shared Slack, Discord, iPhone and Mac notifications. Connecting a self-hosted Jelly explains how.
A team on Jelly's own hosting has been connected from the start, so Housekeeping doesn't show it this section.
Google sign-in
On a Jelly that's connected to Jelly's services, which includes every team Jelly hosts, this section decides whether the sign-in page offers Continue with Google. It's on to start with. You can turn it off, or fill in a Workspace domain to let in only accounts from one Google Workspace domain.
If this section says the manager's Google client has changed, it's asking you to accept the change before Google sign-in carries on. Google sign-in explains each part.
Usage reporting
Once a day, your Jelly sends us a few counts about how it's used. A team that runs its own Jelly can turn this off here. For a team Jelly hosts, the report is part of the service, and there's no switch. Usage reporting lists every figure.
Trial emails
While a team Jelly hosts is on its free trial, this section has the switch for the short emails Jelly sends the Owner to help the team get set up. Turning it off doesn't stop the emails about the trial ending, which are sent either way. The section goes once the team has a plan.
Your Jelly's id and version
The last line on the page gives your Jelly's instance id, the version it runs, and its address. Include it when you write to support about a problem.
What isn't on this page
Some settings belong to whoever runs your team's Jelly server, and aren't on any settings page. They include the instance's address, its mail credentials, and, on a Jelly with no connection to Jelly's services, what Google sign-in and Gmail connections need. If a page tells you something has to be set on the instance, that's the person to ask.
Import from Jelly
Import from Jelly brings a team's mail across from the older Jelly, using its data export. It's in the Settings sidebar only if whoever runs your team's Jelly has turned it on.
Advanced: for whoever runs the server
If your Jelly runs on CARLOS, the platform Jelly's own hosting uses,
the sweep is the /jobs/sweep job. Declare it with
carlos schedule set -name sweep -every 1h -path /jobs/sweep, and
check it's there with carlos schedule ls.
Import from Jelly appears when the server has JAM_JELLY_IMPORT
set to any value.