ProctoringLockoutOutput

Persisted proctoring lockout record with audit fields

  • the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • Computed server-side as startsAt + resolved lockoutDuration (seconds); never accepted from caller.

  • Lockout lifecycle state

    values
    activeexpiredrevoked
  • Set when the lockout was revoked (guide unlock or dispute release); null while active.

  • Platform user who revoked the lockout; null for system/dispute releases and while active.

  • Reason recorded at revoke time (e.g. guide_unlock, dispute_strike_release); null while active.

  • Denormalized slug of the rule that tripped the lockout. Clients render lockout copy from this slug rather than fetching triggeringInsightId. Null when the lockout was created without a triggering rule.

  • LtiApplication ID when scopeType='application'; null when scopeType='global'

  • Lockout scope discriminator

    values
    applicationglobal
  • the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • External Caliper session id of the triggering session. Lets a consumer key a follow-up event (e.g. locked_out_restart) on the same external session id as the rest of the session's events. Null when the lockout has no triggering session or that session was not yet ingested.

  • The field is always null. Use triggeringCaliperSessionId.