Union.ai

PASS consensus from 3 PASS.

One page gives the prerequisite, install command, local config, complete hello.py, run command, and result inspection. One page carries the whole path with no guessing: Python 3.10+, pip install 'flyte[tui]', flyte --version, flyte create config --local-persistence, a complete hello.py, and flyte run --local hello.py main; however all four Next steps links on that page 404 because they resolve against a quickstart/ base that does not exist (for example /get-started/quickstart/core-concepts/_index). The Quickstart provides an unambiguous four-step path (install SDK, configure, write hello.py with TaskEnvironment + @env.task, run locally) with working code and expected output.

PASS consensus from 2 PASS, 1 PARTIAL.

The 10 MiB default appears consistently, and resource ceilings and quota budgets use project-domain scopes. Three pages agree the inline-I/O ceiling is 10 MiB set by max_inline_io_bytes on @env.task, but the Data flow page states 10MB and names a parameter max_inline_io on flyte.TaskEnvironment that appears nowhere else in the SDK reference; the project-by-domain side is exact and consistent, with a full task_resource.min/max key list, an org to domain to project inheritance chain, and the rule that task_resource.max.* is a hard limit that caps rather than rejects an oversized request. Inline I/O ceiling is explicitly 10 MiB default with a configurable override. Project-by-domain quota rules are documented via the Settings hierarchy (org → domain → project) with specific task_resource.max.* keys that are enforced as hard per-task ceilings.

PASS consensus from 3 PASS.

The page says automatic failover needs no correction unless expirations recur on the same run or cluster. A dedicated Leases page shows the literal error string lease expired for action a0 ..., explains heartbeat, grace period, expiration and failover, states that no correction is required in most cases, and gives the one condition that does warrant action, namely repeated lease expirations on the same run or cluster. The Leases page explains the error's cause (heartbeat failure → grace period → lease reaped), why no action is normally needed, and what to check if the error recurs (cluster health, network, or resource provisioning).

PARTIAL consensus from 3 PARTIAL.

The sender is documented, but receiver token checking appears only in a separate webhook app example with different semantics. The send half is exact, including a headers={"Authorization": "Bearer my-token"} example, the four terminal ActionPhase values, and attachment per run via flyte.with_runcontext(notifications=...), but the receive and verify half is absent: the corpus has no delivery log, retry semantics, signature or HMAC, default payload when body is omitted, or local receiver recipe, even though the same page family gives a local aiosmtpd recipe for email, and the run-with-notifications page's only link to the webhook example is itself a 404. Sending a terminal-phase webhook with an Authorization header is documented via notify.Webhook on the Triggers page. However, no documentation shows how to receive and verify such a notification webhook at the receiver; a different webhook pattern (webhook app triggering tasks) shows a receiver with auth but is conceptually distinct, requiring cross-referencing.

PASS consensus from 3 PASS.

The SDK quickstart and migration guide use flyte.TaskEnvironment and @env.task, matching Flyte 2's task model. The SDK reference is versioned (Flyte SDK version 2.0) and its TaskEnvironment entry matches the quickstart's minimum working workflow of flyte.TaskEnvironment plus @env.task with required type hints, though the flyte.notify package page's own quick start uses a @flyte.task(trigger=...) decorator that the SDK function index does not list. The official SDK is the flyte package installed via pip install 'flyte[tui]'. The Quickstart shows a complete working workflow using TaskEnvironment and @env.task, which matches the Flyte 2 task model used throughout the docs.