OtBotRequest
- Engine: SQL (Django model / relational table)
- App: reference
- Table/Collection:
reference_otbotrequest - Verbose name: ot-bot investigation request
A request for the ot-bot agent to investigate a validation row. Raised by the "Investigate with ot-bot" button on /tools/data-validation. The row is recorded here first, then: * posted straight to the Hermes webhook (SENT) when the endpoint is reachable, or * left PENDING for the poller running on the Hermes host to collect (CLAIMED) and acknowledge when it has been looked at - which is how it works from production, where the host cannot reach the agent directly.
| Field | Type | Column/Key | Null/Default | PK | Choices | Notes |
|---|---|---|---|---|---|---|
| id | AutoField | id | — | PK | — | — |
| issue | ForeignKey → ValidationIssue (FK) | issue_id | null | — | — | |
| issue_pk | IntegerField | issue_pk | — | — | The validation row's id, kept even if that row is deleted | |
| check_code | CharField | check_code | — | — | — | |
| competition_key | CharField | competition_key | — | — | — | |
| event_id | CharField | event_id | — | — | — | |
| round_num | IntegerField | round_num | null | — | — | |
| heat_num | IntegerField | heat_num | null | — | — | |
| payload | TextField | payload | — | — | JSON body sent to the Hermes webhook | |
| status | CharField | status | dflt=pending | pending: waiting for pickup; sent: posted to ot-bot; claimed: collected by ot-bot; done: investigated; error: could not send | — | |
| requested_by | CharField | requested_by | — | — | — | |
| previous_status | CharField | previous_status | — | — | The row's status before ot-bot took it on, restored when the… | |
| detail | CharField | detail | — | — | What went wrong, when the send failed | |
| created_at | DateTimeField | created_at | — | — | — | |
| updated_at | DateTimeField | updated_at | — | — | — | |
| sent_at | DateTimeField | sent_at | null | — | — | |
| claimed_at | DateTimeField | claimed_at | null | — | — |
Field names link to their fuller explanation below.
Field details
Click a field name in the table above to jump to its explanation. Fields with no help text yet show a prompt, and are the ones to improve by adding a help_text on the model field, then regenerating.
id
- Engine: SQL
- Type:
AutoField - Column/Key:
id - primary key
No help text yet — add a help_text on the model field and regenerate to fill this in.
issue
- Engine: SQL
- Type:
ForeignKey→ ValidationIssue (FK) - Column/Key:
issue_id - nullable
No help text yet — add a help_text on the model field and regenerate to fill this in.
issue_pk
- Engine: SQL
- Type:
IntegerField - Column/Key:
issue_pk
The validation row's id, kept even if that row is deleted
check_code
- Engine: SQL
- Type:
CharField - Column/Key:
check_code
No help text yet — add a help_text on the model field and regenerate to fill this in.
competition_key
- Engine: SQL
- Type:
CharField - Column/Key:
competition_key
No help text yet — add a help_text on the model field and regenerate to fill this in.
event_id
- Engine: SQL
- Type:
CharField - Column/Key:
event_id
No help text yet — add a help_text on the model field and regenerate to fill this in.
round_num
- Engine: SQL
- Type:
IntegerField - Column/Key:
round_num - nullable
No help text yet — add a help_text on the model field and regenerate to fill this in.
heat_num
- Engine: SQL
- Type:
IntegerField - Column/Key:
heat_num - nullable
No help text yet — add a help_text on the model field and regenerate to fill this in.
payload
- Engine: SQL
- Type:
TextField - Column/Key:
payload
JSON body sent to the Hermes webhook
status
- Engine: SQL
- Type:
CharField - Column/Key:
status - default =
pending; choices: pending: waiting for pickup; sent: posted to ot-bot; claimed: collected by ot-bot; done: investigated; error: could not send
No help text yet — add a help_text on the model field and regenerate to fill this in.
requested_by
- Engine: SQL
- Type:
CharField - Column/Key:
requested_by
No help text yet — add a help_text on the model field and regenerate to fill this in.
previous_status
- Engine: SQL
- Type:
CharField - Column/Key:
previous_status
The row's status before ot-bot took it on, restored when the conclusion lands
detail
- Engine: SQL
- Type:
CharField - Column/Key:
detail
What went wrong, when the send failed
created_at
- Engine: SQL
- Type:
DateTimeField - Column/Key:
created_at
No help text yet — add a help_text on the model field and regenerate to fill this in.
updated_at
- Engine: SQL
- Type:
DateTimeField - Column/Key:
updated_at
No help text yet — add a help_text on the model field and regenerate to fill this in.
sent_at
- Engine: SQL
- Type:
DateTimeField - Column/Key:
sent_at - nullable
No help text yet — add a help_text on the model field and regenerate to fill this in.
claimed_at
- Engine: SQL
- Type:
DateTimeField - Column/Key:
claimed_at - nullable
No help text yet — add a help_text on the model field and regenerate to fill this in.
Generated by docs_models management command for SQL.