# protocols-polling-checks
render pydantic_v2.BaseModel
  Error: --client-protocols['checks.later'].accepted_statuses[1]: The accepted status 201 of 'checks.later' selects no success response of POST /jobs; --client-protocols['checks.later'].accepted_statuses[2]: The accepted status 404 of 'checks.later' selects no success response of POST /jobs; --client-protocols['checks.later'].expires_at: The expiry of 'checks.later' reads integer values, where only a string gives a date and time; --client-protocols['checks.later'].remote_cancel.operation: POST /archives must declare a success response for the remote cancel of 'checks.later'; --client-protocols['checks.poll'].poll: POST /exports must declare exactly one JSON success response for the polling helper 'checks.poll'; --client-protocols['checks.states'].pending[0]: The state 'zero' of 'checks.states' is string, which its state never reads; --client-protocols['checks.states'].failed[0]: The state True of 'checks.states' is boolean, which its state never reads; --client-protocols['checks.unread'].state: The state of 'checks.unread' reads the header 'X-State', which GET /exports/status does not declare; --client-protocols['checks.bindings'].bindings[0].target: The binding 0 of 'checks.bindings' writes the cookie 'session', which carries credentials no helper writes; --client-protocols['checks.bindings'].bindings[2].target: The binding 2 of 'checks.bindings' writes the same target as its binding 1; --client-protocols['checks.bindings'].bindings[3].value.source: The binding 3 of 'checks.bindings' reads the helper's input, which is not supported yet; --client-protocols['checks.bindings'].bindings[4].value.selector: The binding 4 pointer '/nothing' of 'checks.bindings' names no property of the POST /jobs response; --client-protocols['checks.bindings'].bindings[5].target: The binding 5 of 'checks.bindings' gives integer values, which the header parameter 'X-Trace' of GET /jobs/{jobId} does not accept; --client-protocols['checks.dots'].bindings[0].value.literal: The binding 0 of 'checks.dots' gives '..', which makes the segment of the path parameter 'jobId' of GET /jobs/{jobId} a dot segment; --client-protocols['checks.bodyless'].bindings[0].value.selector: The binding 0 of 'checks.bodyless' reads the body of the 202 response of POST /exports, which is no JSON model; --client-protocols['checks.required'].bindings: GET /exports/find requires the querystring parameter 'filter', which no binding of 'checks.required' writes; --client-protocols['checks.required'].result.bindings: POST /reports requires a request body, which no binding of 'checks.required' writes; --client-protocols['checks.unwritten'].bindings: GET /jobs/{jobId} requires the path parameter 'jobId', which no binding of 'checks.unwritten' writes; --client-protocols['checks.unwritten'].result.bindings: The polling helper 'checks.unwritten' writes a request body of POST /notes other than JSON, which is not supported yet; --client-protocols['checks.overlaps'].result.bindings[1].target: The result binding 1 of 'checks.overlaps' writes a target overlapping that of its result binding 0; --client-protocols['checks.fetch'].result.operation: POST /exports must declare exactly one JSON success response for the result of 'checks.fetch'; --client-protocols['checks.header'].result.selector: The result of 'checks.header' reads a header, where only a body pointer reads a result; --client-protocols['checks.union'].result.selector: The result pointer '/labels/rows' of 'checks.union' reads through a union or map, which is not supported yet; --client-protocols['checks.absent'].result.selector: The result pointer '/nothing' of 'checks.absent' names no property of the GET /jobs/{jobId} response; --client-protocols['checks.missing_schema'].result.schema: The result schema '/components/schemas/Missing' of 'checks.missing_schema' does not exist in its document; --client-protocols['checks.other_schema'].result.schema: The result schema '/components/schemas/Report' of 'checks.other_schema' is not the schema its pointer reads; --client-protocols['checks.none_immediate'].immediate_result: The immediate result of 'checks.none_immediate' gives a result, which a helper without a result never has; --client-protocols['checks.immediate'].immediate_result.statuses[0]: The immediate status 201 of 'checks.immediate' selects no success response of POST /jobs; --client-protocols['checks.immediate'].immediate_result.selector: The immediate result of 'checks.immediate' reads models.ExportState, which is not its result type models.Report; --client-protocols['checks.immediate_models'].immediate_result.statuses[0]: The immediate status 200 of 'checks.immediate_models' selects no success response of POST /exports; --client-protocols['checks.immediate_models'].immediate_result: The immediate result of 'checks.immediate_models' reads POST /exports, whose success responses are not all one JSON model, which is not supported yet; --client-protocols['checks.immediate_header'].immediate_result.selector: The immediate result of 'checks.immediate_header' reads a header, where only a body pointer reads a result; --client-protocols['checks.progress'].immediate_result.selector: The immediate result of 'checks.progress' reads models.Report, which is not its result type int; --client-protocols['checks.credentials'].bindings[1].target: The binding 1 of 'checks.credentials' writes the header 'x-api-key', which carries credentials no helper writes; --client-protocols['checks.credentials'].bindings[2].target: The binding 2 of 'checks.credentials' writes the query parameter 'api_key', which carries credentials no helper writes; --client-protocols['checks.credentials'].result.bindings[0].target: The result binding 0 of 'checks.credentials' writes the query field 'api_key', which carries credentials no helper writes; --client-protocols['checks.no_success'].accepted_statuses[0]: The accepted status 202 of 'checks.no_success' selects no success response of POST /archives; --client-protocols['checks.no_success'].immediate_result.statuses[0]: The immediate status 200 of 'checks.no_success' selects no success response of POST /archives; --client-protocols['checks.no_success'].immediate_result: The immediate result of 'checks.no_success' reads POST /archives, whose success responses are not all one JSON model, which is not supported yet; --client-protocols['checks.media'].result.bindings: The polling helper 'checks.media' writes a request body of POST /archives/search, which has no default media type; set the operation's request_media_type; --client-protocols['checks.cancel'].expires_at: The expiry of 'checks.cancel' reads the header 'Expires', which POST /jobs does not declare; --client-protocols['checks.cancel'].remote_cancel.bindings[0].target: The cancel binding 0 of 'checks.cancel' gives integer values, which the header parameter 'X-Reason' of DELETE /jobs/{jobId} does not accept; --client-protocols['checks.cancel'].remote_cancel.bindings: DELETE /jobs/{jobId} requires the path parameter 'jobId', which no binding of 'checks.cancel' writes
