Airing-title automation

Scheduling from AniList

For an airing title, AniList provides the next announced episode and airtime. Omakase uses that information to schedule the next useful check shortly after the episode is expected to air.

The scheduler does not assume a release appears immediately. It can run bounded follow-up checks while:

• configured release sources catch up;
• a provider makes the candidate available;
• a better subtitle-bearing release appears;
• a temporary source outage clears.

What one check does

Each check reuses the same identity and readiness contract as a manual request:

1. confirm the monitored AniList identity and expected episode count;
2. inspect existing accepted inventory;
3. search the configured source pool;
4. skip recently provider-rejected hashes;
5. rank new eligible candidates;
6. verify title, season, episodes, media, subtitles, and playback;
7. publish only a complete, verified improvement;
8. record missing counts and the next check.

The scheduler continues past a failed candidate. One title’s failure does not block unrelated monitored titles.

Finished airing

When AniList reports the season finished, the interface says Finished airing. Omakase still distinguishes the title’s broadcast state from its local readiness state.

A finished season with missing episodes is not complete. It remains visible with an explicit missing count and can continue bounded recovery checks according to the configured policy.

Source and provider exhaustion

Omakase does not claim to search the entire Internet. It searches:

• its built-in anime release source;
• every owner-enabled source exposed through the configured optional catalog service.

If those sources return no eligible new candidates, or if the provider rejects or cannot supply every distinct eligible candidate, the activity receipt reports exhaustion. Verification rules are not weakened to create a green card.

Health and recovery

Health shows whether the scheduler is ready for the next check, currently running, waiting for a backoff window, or needs operator action.

After an interrupted deployment, never clear a scheduler lease by editing SQLite manually. Confirm no sync process is active, take an online SQLite backup, then use the owner-matched application recovery function supplied by the release.

Keep the timer active only after:

• the exact release revision is proven;
• Doctor passes the selected deployment mode;
• credentials are restricted;
• a backup and rollback receipt exist;
• time and timezone configuration are correct.

Read Troubleshooting for stalled checks and partial source outages.