Rules become automations, share codes travel between installs, and the poster cache keeps one copy.
Rules are automations now. Each one says what starts it - a stream event, an inactive account, a new device, a trust score change, a server going down or up, an update, new or upgraded media - and the builder is one page: When, And only if, Then do. A plain-words sentence tells you what you built, and a live check runs it against what's playing without doing anything.
Twenty-one ready-made automations ship with the app. Pick one from the gallery, fill in the blanks, done. The detail page is one form with one save and a run count.
Export any automation as a tracearr1. code and paste it into another Tracearr. Tokens, ids, and server names get stripped and the importer fills in their own; imports start paused after showing what the code does. A code matching a built-in gets a green tick. There's a community gallery at docs.tracearr.com/templates if you want to share yours.
Media added and media upgraded fire off library sync - ~30 s with Plex or the SSE plugin, next sync otherwise. Conditions on type, library, resolution, HDR, codec, audio, and file size. Notification only, and a library's first sync stays quiet.
Opens on what actually ran - Ran, No match, Failed - with who, where, and what happened ("Recorded a violation · Stopped the stream"). Near misses fold under the table, and any run replays into the builder.
-
Per-event checkboxes are gone; each subscription became an automation to the same destination. Fresh installs seed five: stream started and ended, server down and up, new device
-
Settings → General has three update switches: SSE plugin, media servers, Tracearr
-
"is" on a list field accepts a single value; editing an old country rule could fail to save
-
Deleting a destination used inside an if branch is refused; episode and track notifications name the show or artist
-
The poster cache keeps one copy per poster and stops evicting posters that have not changed; a backed-up precache queue and a cache holding three sizes per poster clean themselves up on the first start after upgrading
-
rule.type is null on /api/v1/violations and the public API, as since 2.0; shapes unchanged
-
Stream-start alerts fire at session confirm (~30 s), not first sight
-
A stream paused across the upgrade can get one more paused-too-long alert
-
Posters cache at 360×540 only, and public API poster_url points at that copy with immutable cache headers; IMAGE_CACHE_MAX_MB is a hard ceiling now, not an eviction cap, and IMAGE_CACHE_MIN_FREE_PERCENT (default 10) keeps the disk from filling