Async MotherDuck warehouse provisioning — QA

PR #5209 · captured against a real provisioned MotherDuck warehouse + a real Fivetran connector on local dev. State machine: PROVISIONING → CONNECTED (then sync) or → FAILED (retryable).

1 · PROVISIONING

Clicking “Connect <source>” provisions the MotherDuck warehouse on demand — the row is created immediately in PROVISIONING and Fivetran setup tests run off the request path. Status: “Setting up your warehouse…”.

1 · PROVISIONING

2 · CONNECTOR ATTACHED

The connector (here the dev-only no-auth Webhooks) is created against the warehouse’s Fivetran group and appears under Connectors. This is the real connector-first flow: connect a source → warehouse provisions → connector attaches.

2 · CONNECTOR ATTACHED

· FAILED (review fix)

If Fivetran can’t verify the destination, the warehouse moves to FAILED. The homepage shows a dedicated “Warehouse setup failed” banner with a Retry action — replacing the old generic “warehouse unhealthy” banner that had no recovery path.

· FAILED (review fix)

3 · CONNECTED

When setup tests pass the warehouse is CONNECTED and the initial sync is enqueued.

3 · CONNECTED