Skip to main content

Changelog & known issues

OmniBurrow is in alpha. This page tracks notable releases and documentation updates, newest first, plus a list of issues we already know about.

:::tip Contributors Every meaningful docs change adds an entry here in the same commit — see the repo AGENTS.md. :::

Documentation updates​

2026-07-31 — Troubleshooting​

  • Added Import Errors, Notifications & Reminders, and Camera & Scanning — symptom first, cause second, fix third.
  • Filled in the Known Issues list below, which had been empty. Eight entries, all found while writing these docs against the code.
  • Rewrote the deleted-record answer. There is no undo, and deleting a rabbit also permanently deletes its photos — so the honest advice is to set an ownership status instead of deleting for an animal that simply left your barn.
  • Android battery optimization is the most common reason reminders go missing, even when permission is granted and the switch is on.
  • A scan that says "not in your herd" usually means that rabbit has not synced to that phone yet — not that anything is broken.
  • A failed restore is the safety net working. Row counts are reconciled per table and any mismatch rolls the whole thing back rather than leaving you half-restored.
  • Filled the gaps left on the three older troubleshooting pages, which each carried a "to be expanded" note, and cross-linked all six.

2026-07-31 — Reference​

  • The feature matrix now covers every module, not a third of them — 48 rows across herd, breeding, health, feed and grow-out, business, marketplace, daily work, analytics, sync, and account — and is split into what is mobile-only, web-only, and online-only.
  • Added an export file reference: every CSV in the archive, what each holds, how photos are packaged, and the eight tables that are exported but not restored — email delivery history, import job history, export history, and usage metrics. They are history about your account rather than records of your rabbitry, so re-creating them on a restore would be meaningless.
  • Rewrote the FAQ as 32 questions grouped by cost, getting started and importing, offline and sync, data and privacy, features, and platforms — with structured data so search engines and assistants can quote the answers accurately.
  • Two things people assume are web-only and are not, now stated in the matrix: cage cards (including batch printing) are on both apps with the same renderer, and Clover is on both.
  • Finished the CSV field reference with how to read it and a section on where unmapped columns end up.

2026-07-31 — Clover​

  • Rewrote Clover Assistant around what it can actually do, which is a great deal more than the old page implied.
  • Clover can record work, not only answer questions. It can log a weight, log weights for a whole litter, record a health event, complete a task, or create a litter — each one only after you confirm explicitly. The docs previously described it as read-only.
  • What it can work out, now listed: rank does by productivity or kit survival, rank bucks by offspring growth, rank historical pairings, flag animals below the herd average, find true outcrosses ranked by projected COI, trace which foundation ancestors dominate your herd, report cost per pound of edible meat, and forecast feed use.
  • It is on both apps — a full chat page plus a page-aware floating helper on the web, and a chat screen on the phone. The floating helper can be switched off in settings.
  • It is not a veterinarian, and is explicitly built not to diagnose or prescribe — now a caution rather than a footnote.
  • It only knows what you have recorded, and says so when something is not tracked at all rather than estimating.

2026-07-31 — Sync & Conflicts​

  • Added Sync Diagnostics — what every number on that screen means, and how to tell busy from stuck, which look the same from the outside.
  • Expanded Conflict Resolution with what OmniBurrow decides for you and what it deliberately will not: safe fields merge on their own with the latest edit winning per field, protected fields stop and ask, and the decision is made on the server so both devices reach the same answer.
  • A history backfill still running is normal, not an error. Sync runs in two lanes — core data makes the app usable, then history fills in behind it. That is why a fresh sign-in is usable quickly instead of waiting for years of records.
  • Explained the "deferred" count: records skipped on a pull because you had an unsent local change to the same record. OmniBurrow will not overwrite your own unsynced work, and re-fetches them once your change has uploaded.
  • Queued changes are never discarded — there is no attempt limit that throws work away — and a pending count that will not fall with a good connection is the one thing on that screen worth investigating. A lapsed subscription is a common cause.
  • Why routine syncing is silent: there is no "synced 47 changes" notification by design, so the notification you do get for a conflict is one you will still read.
  • Pointed Sync & Connectivity at the diagnostics screen and sharpened the conflict and outbox entries in the glossary.

2026-07-31 — Account, Billing & Settings​

  • Documented plans, the trial and billing, settings, email preferences, backup, export and deletion, and finished Data Ownership.
  • Closing your account is reversible for 30 days. It builds you an export, emails the links, cancels the subscription at the end of the paid period, and schedules deletion a month out — sign back in within that window and you can undo it. The docs previously said closing could not be undone. Delete all my data is the one that is immediate and permanent.
  • Export works without a subscription; restoring a backup does not. If your access has lapsed you can still request, track, and download an export — your way out is never behind the paywall — but you need an active subscription to restore one.
  • What actually happens when access ends, per app: the web dashboard redirects to your account page; the phone keeps working on its local copy and you can still read and record. Only the exchange with the server stops, and queued edits are held rather than discarded.
  • Corrected the email categories from five to eight, plus the always-on account and security category: transfer invites, sale receipts, waitlist, marketplace, product guidance, weekly task digest (off by default), health alerts, and inventory alerts. Also spelled out that switching a category off affects your buyers, not just your own inbox.
  • Data export links last 7 days, and you can simply request another.
  • Which settings are shared and which are per-device is now stated plainly — growth targets and layouts follow your account, while theme, Quick Log actions, and the reminder hour belong to the device.
  • Corrected the deletion claim on Account Issues and added an "my access ended — is my data gone?" answer there and in the FAQ.

2026-07-31 — Analytics​

  • Documented all the analytics dashboards, each page answering the same two questions: what it tells you, and what you have to record for it to be true — overview, production and does, feed and conversion, health and care, lines and COI, show performance, and profitability.
  • The dashboards tell you when they do not have enough data, and that is now documented as a feature rather than left to be discovered. Each reports a confidence level from its sample size and lists what was missing in plain language — "no feed allocations in period", "FCR requires at least two weight records for linked feed targets". Read those before acting on a figure.
  • Corrected what the health dashboard actually contains. It is Health & Care — body condition, welfare concern flags, nail trims due, and withdrawal windows. The docs previously promised mortality rate, causes of loss, treatment frequency, and age-at-loss patterns. Kit mortality lives on the production dashboard; harvest reasons live on the harvest dashboard; there is no aggregated cause-of-death report built from health events, so the pages say to filter the health hub or export instead.
  • Corrected the production metrics. The docs listed litters per doe per year, survival to weaning, and weaning weight. What exists is litters, total kits, average litter size, average daily gain, misses, false pregnancies, and conception rate per doe, plus herd-wide litter size, kit mortality, and ADG.
  • Per-rabbit profit and loss excludes litter and grow-out feed. Only feed allocated directly to a rabbit lands in its row, so treat the figure as revenue minus directly attributable cost rather than a full cost of production. The app itself flags this, and the page now leads with it.
  • There is no whole-herd profitability dashboard — that view is the finance ledger, whose totals are computed across your filter rather than the visible page.
  • Show placings have no trend chart; comparing seasons is a date-filter change. Grand champions is a herd count, not a period count.
  • Dashboards are summaries, not exports — rankings cap at 100 rows and detail lists at 200. The default window is the last year, and comparisons are against the preceding window of equal length.

2026-07-31 — Daily Work​

  • Documented the daily barn work: Barn Scan (verified and extended), tasks and reminders, calendar export, data entry sessions, Quick Log and search, supply inventory, and the maintenance tools.
  • Search matches different fields on each app, and now the docs say which. Both find a rabbit by name and ear tag; only the phone also matches tattoo and registration number. If a search comes up empty on the web, that is why.
  • A rabbit's cage number is not matched by global search — cage numbers find litters and grow-out groups. Use the search box on the rabbits list to find the rabbit in a cage.
  • Reminders are per device, with your own notify-at hour and time zone, and several tasks due at once arrive as one grouped notification rather than a storm. Snooze offers +1 hour, tonight, or tomorrow, and snoozing moves the reminder, not the due date.
  • A task created offline keeps a local reminder so it still fires with no signal; once it syncs the server takes over and the local one is suppressed, so you get one reminder rather than two.
  • Calendar entries are all-day events with no alarm of their own — reminding you is the app's job, and an alarm on the event would mean two notifications for one task. Completing a task removes its entry; reopening brings it back.
  • Server reminders and calendar export need a fresh app build, not an over-the-air update, since both depend on native components. Noted on both pages rather than promised as already live.
  • Merging is permanent and lives on the rabbit, not the tools screen — now a :::danger, because there is no unmerge.
  • Inventory alerts have thresholds you have to set: an item with no reorder threshold never reads as low, and one with no expiry date never reads as expiring. Expiring-soon means within 14 days.
  • Added seven daily-work rows to the feature matrix and expanded the Quick Log and data-entry entries in the glossary.

2026-07-31 — Shows & Cage Cards​

  • Documented shows and entries and cage cards.
  • Corrected a claim we had been repeating: batch cage-card printing is not web-only. Both apps print single cards and batches, using the same renderer, so a card looks identical whichever produced it — and the phone does it offline from its own print-selection screen. The feature matrix and the contributor rules both said otherwise.
  • The third leg is handled for you. Saving the entry that takes a rabbit to three legs records the grand-champion date, remembers which entry earned it, and prompts for the GC number. Legs won before you started using OmniBurrow can be added in bulk, one to eight at a time.
  • Two different "show class" fields, now told apart. The class on an entry is free text you type, so it matches what the show called it. The class on a cage card is computed from the breed's scheme, the date of birth, and the show date.
  • Spelled out the class boundaries: four-class is junior under 6 months and senior from 6; six-class — the large and giant breeds — adds intermediate from 6 to under 8 months, senior from 8.
  • Missing details print as write-in lines on a show card rather than being dropped, so a rabbit with no recorded date of birth still gets a labelled blank.
  • A rabbit inside a withdrawal period prints the warning on its barn card, with the clear date.
  • Added show and cage-card questions to the FAQ, and leg, junior/intermediate/ senior entries to the glossary.

2026-07-31 — Grow-Out​

  • Documented feed tracking, grow-out groups, and processing and harvest.
  • Buying feed is not the same as allocating it. Only allocation — this much feed, to these animals, over these dates — produces a conversion ratio. Bought-but-unallocated feed shows as cost and nothing else, and the page now says so plainly.
  • Three ways to end up with a blank FCR, all of them now spelled out: feed never allocated, fewer than two weights on a target inside the period, or a grow-out group with no litter linked — because group feed is attributed to the group's litter when gain is calculated.
  • A grow-out group has no per-animal roster. You do not add rabbits to one individually; the linked litter is the association. Worth knowing before you plan around it.
  • Feed schedules draw down your stock automatically — daily usage is amount per feeding times feedings per day — and those movements count as feed in your conversion figures when the inventory item has pounds per unit set. This is the opposite of medication stock, which never decrements.
  • Dress-out percentage and its companions are calculated, not typed: dressed over live, edible meat over dressed, edible meat over bone, and age at harvest from date of birth to processing date.
  • Processing snapshots each animal's date of birth, sire, dam, and breed onto the record, so harvest results stay attributable years later even if the parent records change.
  • Added feed, grow-out, and processing rows to the feature matrix, and sharpened FCR, dress-out, grow-out group, and a new allocation entry in the glossary.

2026-07-31 — Health & Medications​

  • Documented health events, treatments and withdrawal periods, medication inventory, and care observations.
  • Withdrawal is enforced, not just tracked. Recording an animal as processed while it is still inside a withdrawal window is refused — getting past it needs a deliberate override plus a written reason, and both are stored on the processing record.
  • The clear date depends on a number you enter. It is the last day of the course plus the meat withdrawal days recorded on the medication. Leave that field blank and the treatment gets no clear date and the processing block never fires. That condition is now stated prominently on three pages, because it is the difference between a safety net and the appearance of one.
  • Corrected an assumption about the medicine box: giving a dose does not reduce your stock. Quantity on hand is a number you maintain yourself; nothing decrements it. The docs previously implied doses drew inventory down.
  • Spelled out the date arithmetic — a five-day course starting the 1st ends on the 5th, not the 6th — and that a rabbit's withdrawal date is the latest across all its treatments, so overlapping courses cannot shorten it.
  • Health event costs do not reach your ledger. The cost field lives on the event; enter the expense separately if you want vet bills in your books.
  • Explained why care observations and health events both exist — scored welfare checks that show a trend, versus a titled record of an incident — and what the observations actually feed: average body condition, nail trims due, and a concern-flag count for poor or absent appetite.
  • Added health rows to the feature matrix, sharpened the withdrawal-period entry in the glossary, and added two health questions to the FAQ.

2026-07-31 — Marketplace & Transfers​

  • Documented the marketplace for the first time: listings, breeder storefronts and reviews, and pedigree transfers between accounts.
  • Published listings are visible to anyone on the internet, not only to signed-in OmniBurrow users. Your rabbitry name, city, state, and bio are public; your email address and phone number are not, and buyer messages are relayed to you instead. Nothing is public until you press publish.
  • Listings cover more than rabbits — litters, stud service, supplies, cages, hides, meat, and wanted ads — and only the type and a title are required. A price of 0 means "contact for price".
  • Accepting a transfer marks your copy of the rabbit Sold, and its ancestors arrive in the buyer's herd as reference rabbits. Transfers can be limited to three generations rather than your full recorded lineage, and a rabbit transferred back to a previous owner is reactivated rather than duplicated.
  • Reviews work differently from most marketplaces, so both facts are now stated plainly: any registered member can review you without having bought anything, and there is no seller response. Reporting a review is the only route, and removal is decided by OmniBurrow.
  • Invite links expire after 14 days and can be resent; a cancelled or undone sale kills the claim link, so tell the buyer.
  • Added marketplace and storefront rows to the feature matrix, two questions to the FAQ, and corrected the Marketplace paragraph on What Is OmniBurrow?.

2026-07-31 — Business​

  • Expanded the Business section: contacts, waitlist, deposits and sales, and the finance ledger.
  • Corrected where a deposit lives. The docs said to open a contact and add a deposit. A deposit belongs to a waitlist entry, so the order is contact → waitlist entry → deposit. The old wording left people looking for a button that is not there.
  • Wrote down what each deposit status does to your books — received puts pending money on the ledger and emails the buyer a receipt, refunded removes it and emails a refund notice, forfeited keeps the money and relabels the row, applied credits it to the sale.
  • Documented what undoing a sale actually reverses, including the part that catches people out: the waitlist entry only reopens if a deposit was applied. A sale with no deposit leaves its entry marked fulfilled.
  • Explained why sale, purchase, and deposit rows cannot be typed by hand — the sale flow writes them, which is what keeps the ledger and the animal records from disagreeing.
  • Flagged the 90-day default window on the web ledger, so a missing older transaction reads as a filter rather than lost data, and noted that the summary totals are computed across the whole filtered set rather than the page on screen.
  • Added undo-sale and buyer-email rows to the feature matrix, and selling questions to the FAQ.

2026-07-31 — Breeding & Litters​

  • Expanded Breeding & Litters: recording breedings and kindling, tracked kits versus phenotype buckets, predicting offspring, and weaning through graduation.
  • Wrote down the whole task chain a breeding sets off and the day counts behind it: palpate at 14 days, nest box at 27, expected kindling at 31, check the nest box the day after kindling, re-breed check at 35, wean at 42, separate males at 56 — all adjustable in herd settings.
  • Explained what the variety prediction numbers actually mean. The list is capped at the top 12 and then scaled to add up to 100, so the figures are shares of that list rather than absolute probabilities, and anything under 2% is dropped as noise.
  • Clarified what graduation carries across — parents, the doe's breed, the resolved ARBA variety, the litter's kindling date as the birth date, the kit's genetics, and its weights — and that the litter's live-kit count drops by one when it happens.
  • Documented graduating offline: the kit is marked graduated immediately, but the new rabbit record appears once the change syncs.
  • Dead kits is calculated, not typed — total born minus live kits — and live kits cannot exceed total born.
  • Selling several kits from one group splits the price across them, creating a rabbit record, a finance row, and a pedigree for each, rather than one lumped sale.
  • Added kit graduation and sell-from-litter rows to the feature matrix, and noted there that the web breeding simulator needs a connection while the mobile one does not.

2026-07-31 — Herd​

  • Expanded the Herd section: rabbit records, pedigrees, weights and average daily gain, photos, and lines.
  • Wrote up the ARBA readiness check on the pedigree view — what it verifies (left-ear tattoo, a complete three-generation tree, consistent breed, recognized varieties, names within 30 characters, pedigree weights in pounds.ounces form, and the six-month age requirement) and the three things it deliberately leaves to a registrar.
  • Documented how the projected butcher date is actually calculated, including that it falls back to date of birth plus your target butcher age when a rabbit has no weight yet, and that it reads today rather than a stale date once the animal is at target weight.
  • Warned that deleting a rabbit permanently deletes its photos. Setting an ownership status keeps the record and its history; deleting does not.
  • Explained merging duplicates properly — what gets re-pointed to the survivor, that the survivor's own values always win, that you cannot merge a rabbit with its own ancestor or descendant, and that it is online-only on both apps.
  • Set out how offline photos really work: the mobile app caches images as you view them, up to 500 MB, so a photo you have never opened on that phone will not be there in the barn.
  • Added pedigree PDF, merge, and photo rows to the feature matrix.

2026-07-31 — Migrating In​

  • Added step-by-step migration guides for Evans Rabbit Register, Kintraks, Everbreed, and plain spreadsheets — what comes across field by field, what the file needs to look like, and what each review-screen warning means.
  • Rewrote Migrating In around the question you actually have: which of the three ways in matches what you have, and what order to run them in. Herd file first, pedigree documents last — that ordering is what stops you ending up with two copies of every grandparent.
  • Filled in the CSV field reference — every field of all five record types, which are required, the column names that get matched for you automatically, and the date, weight, money, sex, and status formats the importer accepts without cleanup.
  • Corrected how duplicates are detected. The docs said an import matched on tattoo, name and date of birth, registration number, or a sire/dam combination. It matches on registration number, then ear tag, then name plus date of birth — there is no sire/dam rule.
  • Clarified pedigree import's ancestor matching: an extracted ancestor is only linked to a rabbit you already own on an exact registration number or ear tag. A name-and-date match is offered as a suggestion instead, so two different rabbits that share a name are never silently merged. A linebred ancestor appearing twice on one pedigree becomes one rabbit, not two.
  • Noted that program import covers more on the phone. The web app imports rabbits and contacts; the mobile app also imports litters, weights, and finance rows. The feature matrix said only "yes" for both.
  • Added import questions to the FAQ — whether your current program can be imported, whether importing creates duplicates, what leaves your device, and where unmapped columns end up.

2026-07-29 — Accuracy pass​

We re-checked every finished page against the apps themselves and corrected what did not match:

  • Per-rabbit profit and loss is a mobile dashboard, not a web one. The web Analytics hub has seven tabs — overview, production, harvest, feed, lines, shows, and health & care — and the docs said otherwise in three places.
  • Corrected what search matches. Rabbits are found by name and ear tag, contacts by name, email, or phone, and litters and grow-out groups by cage number. Searching a cage number does not find the rabbit in it.
  • Corrected restoring a backup on the web — it is Account → Import from backup, not the Import area.
  • Corrected importing several pedigrees at once on the web: the main drop zone takes one document (PDF or photo); Import multiple PDFs is a separate route and takes PDFs only.
  • Password reset is web-only. On the phone, sign in with the emailed link, or reset on the web first. The docs previously implied the phone could reset a password.
  • Clover needs a connection on both apps; the feature matrix implied otherwise.
  • Fixed: program (CSV) import on the phone now opens offline. Writing this page up turned up a real bug — the Import row in the More menu was locked behind having a connection, even though your file is read and imported entirely on the device. Barn imports work now; only the optional AI mapping suggestion needs signal. (Needs the next app build to reach your phone.)
  • Removed the mobile install instructions. The app is not publicly available yet, so The Mobile App now covers what it is for, signing in, and the first sync. Install links go on that page when it is released.
  • Added the first web-app screenshots — the dashboard with its side menu, and the add-rabbit dialog. The add-rabbit screenshots now sit inside the Web/Mobile tabs, so you see the platform you picked instead of always seeing a phone.
  • Smaller corrections to the peanut (Dw/Dw) wording, the storefront name, and the web add-rabbit form description — which does have named sections after all: Identity, Breed & Appearance, Lineage, Details, and the optional ones below them.

2026-07-27 — Core Concepts​

  • Added How Your Records Relate — how rabbits, litters, kits, buckets, contacts, and money connect, and why fixing one parent corrects every pedigree below it.
  • Added a rabbitry glossary covering breeder vocabulary, OmniBurrow-specific terms, and the measurements the analytics are built on.
  • The Genetics Engine page is now written in full — the 13 colour loci and their dominance orders, how genotypes are inferred from your own herd, why a grandparent's recessive counts for 50% and a great-grandparent's for 25%, how the top-12 variety predictions are built, and how coefficient of inbreeding is calculated.
  • ARBA Breeds & Show Classes now spells out the four-class and six-class divisions, which breeds are six-class, and exactly how a rabbit's class is worked out from its date of birth and the show date.

2026-07-27 — later​

  • Search now works on the web app too. Press ⌘K (Ctrl-K on Windows and Linux) or click Search in the top bar to look across rabbits, litters, contacts, inventory, and grow-out groups at once, and to jump straight to any screen. It matches on name, ear tag, cage number, and a contact's email or phone. The mobile app's search is unchanged and still works offline.
  • Corrected the docs, which had wrongly said search was in the header of both apps before this shipped.

2026-07-27​

  • Expanded Getting Started: account setup, installing the mobile app, adding your first rabbit, a map of both apps, and a first-week checklist — with the first real screenshots in these docs.
  • Added the first FAQ answers, covering imports, iPhone availability, where to create an account, cost, and breed support.
  • You can now set your rabbitry name on the web, under Settings → Rabbitry name. It was previously only reachable from the mobile app, even though it is the name printed on your pedigrees and cage cards.

2026-07-26​

  • Added What Is OmniBurrow? — a single page that covers what the software does, who it's for, how the web and mobile apps differ, how your data stays yours, and what it costs (14-day free trial, then $9.99/month, subscribed on the web).
  • Corrected the Feature Matrix: the Clover assistant is available on the web app as well as mobile — it was previously listed as mobile-only.
  • Reorganized the whole documentation site so every part of OmniBurrow has a home. New sections for Herd, Breeding & Litters, Health, Grow-Out, Business, Daily Work, Analytics, Sync, Account & Billing, and Reference. Pages that moved still work from their old links.
  • Added placeholder pages for everything still to be written — around 50 of them — so you can see what is coming and nothing is a dead end. Each one describes what the feature does today and is marked as in progress.
  • Platform & Feature Parity is now Feature Matrix under Reference, and every page now shows when it was last updated.

2026-07-22​

  • Updated Program Import for the shipped Evans XML, Everbreed CSV, and new Kintraks profile. Documented five-type generic/manual mapping, loss-preserving unknown columns, and the optional privacy-limited AI mapping suggestion for exports whose schemas are not publicly available.

2026-06-20​

  • Restructured the documentation: added a Welcome page, a Migrating In section, a Platform & Feature Parity reference, and new guides for Barn Scan, Predict Offspring, Deposits & Sales, Conflict Resolution, Account & Backup, Shows & Cage Cards, and the Clover assistant.
  • Corrected the import documentation to match the app: there are three import tools — CSV import (Everbreed profile + generic spreadsheets), pedigree import (PDF/photo), and restore from backup (ZIP).
  • Added on-device search and platform (Web/Mobile) toggles to guides.

Known issues​

We're tracking these — no need to report them again.

  • Task reminders and calendar export need a fresh app build. Both depend on native components, so an over-the-air update cannot switch them on. If your Settings → Reminders screen does not offer them yet, that is why. See Notifications & Reminders.
  • Search finds different things on each app. Both find a rabbit by name and ear tag; only the phone also matches tattoo and registration number. A registration number that finds a rabbit on your phone may return nothing on the web. Use the rabbits list search as a fallback.
  • A grow-out group with no litter linked reports no feed conversion. Group feed is attributed to the group's litter when gain is calculated, so a group without one contributes cost but no gain and its FCR reads blank — which looks like poor conversion rather than missing configuration. Link the litter when you create the group. See Grow-Out Groups.
  • Per-rabbit profit and loss excludes litter and grow-out feed. Only feed allocated directly to a rabbit appears in its row, so the figure is revenue minus directly attributable cost rather than a full cost of production. See Profitability.
  • Health events are not totalled into any dashboard. There is no cause-of-death or treatment-frequency report; kit mortality lives on the production dashboard and harvest reasons on the harvest dashboard. To count events by type, filter the health hub or export.
  • Medication stock does not decrease when you record a dose. Quantity on hand is a number you maintain yourself. Feed on a schedule does decrement automatically, which makes the difference easy to trip over. See Medication Inventory.
  • A medication with no withdrawal days set produces no withdrawal block. The processing gate is computed from the number you entered, so leaving it blank silently disables the safety net for that medication. See Treatments & Withdrawal Periods.
  • Android battery optimization can silently suppress reminders even with notification permission granted. Excluding OmniBurrow from battery optimization fixes it.

Format: add a ### YYYY-MM-DD heading at the top of "Documentation updates" (or a product "Releases" section) for each change, with plain-language, user-facing bullets.

Last updated on