Request a branded demo

Modules

Catalog Pathways Curriculum Board Essentials Free Assist Coming soon

Catalog

Digital catalog Program pages Courses Search Publishing workflow

Pathways

Career exploration Wage data Program outcomes Student discovery Transfer articulation

Curriculum

Proposals Approvals Vote records Evidence archive Catalog year lifecycle
Capabilities MCP Coming soon API and exports Integrations College branding
Platform overview How the modules share one record, and why that matters at publish time.
Packages Compare Catalog Pathways Curriculum Academics
Academic Affairs Catalog governance Curriculum approvals Accreditation evidence
Catalog & Curriculum Teams Publishing workflow Course and program updates Version control
Enrollment & Marketing Program discovery Career outcomes Search and conversion
Information Technology WordPress ownership Data exports SIS compatibility AI and API readiness
Need help choosing? Tell us what is hardest to manage today and we will recommend a package and setup path. See it in your own colors Request a demo We stand up a full Kenii site carrying your logo and colors, loaded with demo catalog content, so your team can click through the real thing instead of watching a slide deck.

Proof

Why colleges choose Kenii Compare with incumbents Customer stories
Documentation

3.14.2

A catalog PDF made by an older engine is now rebuilt until a build succeeds, and a queued rebuild can never overwrite a PDF the college uploaded.

  • Fixed **An old catalog PDF can no longer stay public after an update.** Each generated catalog records the engine that built it, and only a successful build writes that record. Once an hour Kenii queues a rebuild for any generated catalog made by an older engine, so a rebuild that fails is retried rather than forgotten.
  • Fixed **A rebuild never overwrites an uploaded catalog PDF.** The build now checks for an uploaded PDF when it runs, not only when it is queued, so a PDF uploaded while a rebuild was waiting stays in place.
  • Fixed **A build that keeps failing stops after three tries** instead of retrying every hour, and the reason is kept on the catalog year's PDF status for an admin to see. A later successful build clears it.
  • Fixed New rail `tests/pdf-rebuild-heals.php` builds the active catalog, then proves a stale file is queued, a real failed build is counted and retried up to three times, an uploaded PDF is refused and left byte-for-byte untouched, a current file and a year with no generated PDF are left alone, and the check waits an hour. It restores every record and file it touches, and goes red when the success record, the upload guard or the retry cap is removed.