A feed that does not come is asked again, and a "not found" from it is no longer taken at its word (0.1.16). The time of day of a channel's latest 15 uploads comes from the channel's public feed — and so do their description with details: "figures" or "list", and their unrounded views and likes with "list". On 2026-10-08 — by our run records from about 01:25 UTC, and still at our last reading at 03:21 — YouTube's feed service answered "not found" or "server error" for channels that have a feed: of 40 feeds that had answered the day before, 8 answered a single request at 02:01 UTC and 14 at 02:25. Until this build a "not found" was read as "this channel has no feed", so the rows came without those values and without a word about it. Now the feed of a channel that has videos is asked up to five more times (that brought 25 of the 40 at 02:01 and 39 at 02:25; while a run's last channels bring next to no feeds — at 02:58 the service was down almost altogether — it is asked once more instead of five times), and when it still does not come the status message says "The feed of N channels did not answer: their latest uploads come without …", naming what is missing at the run's details level — the time of day; with figures the description too; with list also the likes, the date of an upload older than a day, and the unrounded view counts. (When the feed gave no answer at all the message already said so, but named only the time of day.)
Wording of a run's last word (0.1.16). A run that delivers nothing used to say "nothing charged". The run-start event is charged for every run, so the message now says "no rows charged". Nothing about charging itself changed.
README corrected after an independent fact-check (0.1.16): 20 statements were wrong or said more than the measurements do, 10 had no record behind them. Among them: a live stream that the channel's feed lists does carry a view count; with details: "list" an upload under a day old is dated from the list; a fresh upload can keep the list's rounded view count although it is in the feed; the restarted test run had 92 rows, not 76, when it was restarted; "10,000 channels a run" is the input limit, not a measured run. The full list is in the Actor's QA record.
A run that delivers nothing says why in its dataset too. When every video was filtered out, a run used to end with an empty dataset and the reason in its status message only. It now also writes one free status row with that message, as the comments and search Actors of this series do, so a call that reads only the dataset is not left with an empty answer. An "only new" run that finds nothing new still leaves the dataset empty.
A killed run of an "only new" list is made up for. A run that is killed (a timeout, the memory limit) cannot save the last videos it delivered. The list's next run now reads them back from that run's dataset before it starts, so they are not delivered a second time. The four sibling Actors already did this; this build brings it here.
commentsOff is described more exactly: it is true when the video's page shows no comment section — comments are turned off, or the video is for members only. (The README used to name "a stream in progress" as a reason; a stream on air has a comment section unless its owner turned comments off.) The values are the same.
README rebuilt in the foXLabs layout: use with AI agents (Apify MCP server, agentic payments), getting started, use cases, integration, a price table, legal notes. The measured figures are the ones of 2026-10-07.
