PendingQuestion

@forge/monorepo

---

@forge/monorepo / backend/src / PendingQuestion

Type Alias: PendingQuestion

PendingQuestion = object

Defined in: backend/src/hitl/index.ts:9

Properties

answeredAt?

readonly optional answeredAt?: string

Defined in: backend/src/hitl/index.ts:23

---

answers?

readonly optional answers?: Readonly<Record<string, QuestionAnswer>>

Defined in: backend/src/hitl/index.ts:25

A value may be a string or an array — see QuestionSpec.multiple (#155).

---

createdAt

readonly createdAt: string

Defined in: backend/src/hitl/index.ts:22

---

id

readonly id: InteractionId

Defined in: backend/src/hitl/index.ts:10

---

questions

readonly questions: readonly QuestionSpec[]

Defined in: backend/src/hitl/index.ts:21

The specs as asked — QuestionSpec, not a narrower copy of it (#163).

This was an inline duplicate carrying only key, prompt and options, so when multiple and allowOther were added to QuestionSpec they were stored and read back by the adapters and then dropped on the floor here. Anything reading a pending question — the GraphQL query, a host's own UI — saw a multi-select as a single choice, with nothing in the types to say so.

---

runId

readonly runId: RunId

Defined in: backend/src/hitl/index.ts:12

---

tenantId

readonly tenantId: TenantId

Defined in: backend/src/hitl/index.ts:11