Interface: FactoryResetResponse
@kortexya/reasoninglayer / FactoryResetResponse
Interface: FactoryResetResponse
Section titled “Interface: FactoryResetResponse”Defined in: src/types/admin.ts:35
Response for the factory-reset operation.
Remarks
Section titled “Remarks”Reports exactly what was wiped across all storage backends so operators can verify the operation succeeded.
Properties
Section titled “Properties”artifactFilesDeleted?
Section titled “artifactFilesDeleted?”
optionalartifactFilesDeleted?:number
Defined in: src/types/admin.ts:78
Number of retained RDF artifacts erased through the configured bucket provider. Absent when the engine did not report it.
bindingsDeleted?
Section titled “bindingsDeleted?”
optionalbindingsDeleted?:number
Defined in: src/types/admin.ts:62
Number of SQL ontology bindings dropped across all tenants.
cacheCleared
Section titled “cacheCleared”cacheCleared:
boolean
Defined in: src/types/admin.ts:46
Whether the cache (Valkey / in-memory) was flushed.
dmPairingStateDeleted
Section titled “dmPairingStateDeleted”dmPairingStateDeleted:
number
Defined in: src/types/admin.ts:97
Number of DM pairing records erased across all tenants: channel policies, allowlisted senders and pairing requests, summed.
Remarks
Section titled “Remarks”Counted through the pairing store before the table truncate, as FactoryResetResponse.inboxItemsDeleted is.
inboxItemsDeleted
Section titled “inboxItemsDeleted”inboxItemsDeleted:
number
Defined in: src/types/admin.ts:87
Number of unified-inbox items erased across all tenants.
Remarks
Section titled “Remarks”Counted through the inbox store before the table truncate, so the count is real for a durable and for an in-memory engine.
message
Section titled “message”message:
string
Defined in: src/types/admin.ts:37
Human-readable summary message.
postgresTables?
Section titled “postgresTables?”
optionalpostgresTables?:string[]
Defined in: src/types/admin.ts:59
The tables that were truncated.
Remarks
Section titled “Remarks”Discovered from the live schema rather than hard-coded, so this is the only way for a caller to tell a complete reset from one whose discovery came back short.
postgresTablesCleared
Section titled “postgresTablesCleared”postgresTablesCleared:
number
Defined in: src/types/admin.ts:40
Number of PostgreSQL tables that were truncated.
qdrantCollectionsDeleted
Section titled “qdrantCollectionsDeleted”qdrantCollectionsDeleted:
number
Defined in: src/types/admin.ts:43
Number of Qdrant vector collections deleted.
sourceFilesDeleted
Section titled “sourceFilesDeleted”sourceFilesDeleted:
number
Defined in: src/types/admin.ts:72
Number of uploaded source files erased across all tenants.
Remarks
Section titled “Remarks”The upload store holds files, not rows, so no table truncate reaches it.
A store that cannot be erased fails the reset with 500 instead of
reporting a clean one.
tenantStatesCleared
Section titled “tenantStatesCleared”tenantStatesCleared:
boolean
Defined in: src/types/admin.ts:49
Whether the in-memory tenant inference states were cleared.