Problem code 'ready-timeout' ​

Contract 2.0.0 · package sha256 a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e · generated from configurator-runtime.d.ts, tables/problems.json and services/onsite-scripter/scripts/contract-docs-what-to-do.json by services/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.

A member of ProblemCode · stable · since 2.0.0

Readiness expired: the commit shows with stand-ins or old looks until assets decode.

What to do ​

The commit shows with stand-ins or old looks until its assets decode; nothing rolled back. Before a session.capture() that must show final pixels, await session.idle(); for a transaction, give TransactionOptions.readyTimeoutMs more time (default 4000).

await session.idle();
upload((await session.capture({ size: { width: 1200, height: 900 } })).image);

Where the declaration names it ​

• CaptureResult.problems: 'ready-timeout', or 'asset-failed' for a slot drawn with the stand-in of a detail map that failed).

The set is open: handle a code you don't know ('other').

Recorded by ​

• the table row failure-matrix/cases/readiness-expiry (tables/failure-matrix.json)
• the table row hold/cases/case-1 (tables/hold.json)