Change freshness, thresholds and outcome settings without a new version
Freshness settings, thresholds and outcome settings are not part of the definition, so this creates no version.
- Thresholds replace the judgment’s whole set of named thresholds
(
{}removes them all). They apply at the next read to every answer, including answers already computed, with no evaluation. Every change is an audit event. A recommended threshold (GET .../thresholds/recommend) is applied this way. A threshold that another judgment’s relation reads (a roll-up) is the exception: changing it withoutconfirm: truereturnsdownstream, what it would re-judge, and changes nothing, the rest of the request included; with it, the thresholds apply and aresyncjob re-judges the readers whose context now reads differently. - Switching to
on_changeneeds answers for every document: withoutconfirm: trueit returns a backfill estimate for the documents with no current answer and changes nothing, thresholds included; with it, the settings apply and the backfill job starts. For an entity judgment the estimate also hasreplay, what the judgment would cost a month from then on, and a confirmed switch whose replay is more than the namespace’s budget isbudget_exceeded. max_wait_mssets the debounce ceiling.fanoutsets which judged documents a change to a referenced document re-judges, and when. Keys you send replace those keys, and the others keep their values. It never starts a job and never needsconfirm, not even to raiserolling_limit, and deferred fan-outs catch up once the window has room. The response’sjudgment.fanout_sourcessays where each value in effect comes from.outcomessets how outcomes are read and derived, and replaces the whole setting:implicit_negativeson abooljudgment with a horizon, andrules, which derive outcomes from the judged document’s own writes, such as an account whoseattributes.statusbecomescancelled. Rules apply to writes from then on, never to earlier ones. The setting is refused on a namespace that inherits the judgment (set it on the template’s prefix path), andruleson the template’s prefix path too. Settingrulesneeds the Team plan or above (plan_required, 402); clearing them ("rules": []) never does. After a downgrade takes effect, rule outcomes observed from then on are kept but not used, and the calibration report counts them asrule_outcomes_paused.
On a namespace that inherits the judgment from a template, this sets that namespace’s own override, which applies to it alone. On the prefix path it changes the template’s settings for every namespace that has no override.
Authorizations
An organization API key. Keys carry a role (read_write or
read_only) and may be restricted to a namespace prefix such as
acme/*, or to one namespace such as acme/prod/tenant_1. A prefix
matches on a / boundary: acme/prod/tenant_1* covers
acme/prod/tenant_1 and everything under acme/prod/tenant_1/,
never acme/prod/tenant_12.
Headers
One key per logical request, reused only on its retries. A key
belongs to one request: within your organization, the same method,
path, query and body. For 24 hours after a successful response, a
request with the key and the same body gets that response back
verbatim, with Idempotent-Replayed: true, and runs nothing. Only a
successful response is kept, so the retry of a request that failed
runs again. While the first request runs or its response is kept,
the key with a different request is idempotency_key_reused (422).
A request sent while one with its key is still running is
rate_limited with Retry-After: 1, without running: retry it to
get the first one's response. In the rare case the key can't be
checked, the request runs as if it had none.
1 - 255Path Parameters
A namespace name, or a template prefix ending in /*, with any
/ sent as %2F: acme%2Fprod%2Ftenant_123 or acme%2Fprod%2F*.
A namespace name, or a template prefix: a namespace path ending in
/*, such as acme/prod/*, which every namespace under acme/prod/
inherits judgments from. Up to 256 bytes. Never exactly
. or .., which a URL path can't carry.
1 - 256^(?!\.\.?$)[A-Za-z0-9._:/-]+(/\*)?$A judgment, attribute or threshold name. Names are path segments in field references, so they never contain ..
1 - 128^[A-Za-z0-9_-]+$Body
- Option 1
- Option 2
- Option 3
- Option 4
At least one of freshness, thresholds, outcomes and escape_alert.
Settings, not part of the definition. Changing them creates no version.
Replaces the judgment's whole set of named thresholds; {} removes them all. Applies at the next read, with no evaluation and no new version. Changing one that a reader's relation names needs confirm and runs a resync job.
Replaces how outcomes are read and derived, rules included. The next nightly fit and every report use it, and rules apply to writes from then on; no version is created.
A setting of a fixed-option choice: when the
share of its answers over the last 7 days that are
none_of_the_above rises above this, the judgment gains the
taxonomy_drift warning and the events feed one
judgment.taxonomy_drift. Null (the default) turns it off. Nothing
changes on its own: run discover when you want proposals.
0 < x <= 1Required to switch to on_change, which starts a backfill, and to change a threshold a reader's relation names, which starts a resync job.
Response
The settings were applied, or an estimate was returned.