Environment
Infrastructure
Background Jobs
| Job | Status | Started | Duration | Lines | |
|---|---|---|---|---|---|
| Loading... | |||||
Recent pipeline jobs
| Name | Status | Active | OK | Fail | Duration | Owner | Image | Age | |
|---|---|---|---|---|---|---|---|---|---|
| Loading... | |||||||||
Queues
Import Scan
When reprocess is enabled, it runs on this environment’s own models: deployed model rows are imported from shared dev (never prod; nothing to import when this is shared dev) and missing weight files are copied from dev-pensa.
Reprocess Scan
Resets scan status and triggers the pipeline for a scan already in this environment. Always syncs fixed-path recon weights (DeepLSD, ALIKED, LightGlue) into MinIO dev-pensa under the env prefix. When the scan routes to DBOS (or leftover DBOS rows exist), also deletes matching dbos.workflow_status ids (scan-{id}*, shelf-complete/OCR/KPI by SSP) so reprocess is not idempotent-skipped. A dbos_parent scan deletes no DBOS rows: it reprocesses as a new attempt scan-{id}.a<n+1> (an active attempt is cancelled first) and earlier attempts stay inspectable. With “Import missing models”, also imports deployed detector/router/OCR DB rows from shared dev (never prod) and pulls those weight files from dev-pensa. Set Pipeline override to route this reprocess to a specific transport (e.g. dbos) by writing scan_metadata.pipeline_name before upload-complete; leave it blank to keep the scan’s current pipeline.
Scans with recent activity
| Scan | Store / Shelf | Age | Duration | Last event | Stage progress | |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Pods
| Name | Status | Ready | Restarts | Age | Image | Node | |
|---|---|---|---|---|---|---|---|
| Loading... | |||||||
Lower-frequency import flows. The two most common actions (Import Scan and Reprocess Scan) live on Home.
Import Project
Core tables (accounts, users, categories, packages, labels) are always imported. Select additional sections:
Import Planogram
Imports planogram + planogram_facing_position rows + referenced products (objects). Banner / store / shelf chain is auto-resolved via the planogram's FKs. Use this to seed Studio / facing / extapi work with realistic prod POGs without going through the full scan pipeline.
Import Users
Import ML Models
Imports deployed detector, SC, OCR, and router models with weights from source S3 to MinIO.
System Object Sync
What this is: Detector-emitted marker objects (rows of the
object table where object_type <> 'CPG' — e.g.
Marker, Rotated, Box End, Shelf Tag,
CPG Unknown / Wrong / Not Found). They are referenced by every
recognition output through object_volume → resolved_volume_inference → observation.
Why you might need to run it: if any of these rows is missing
locally, resolver-runtime crashes with a
ForeignKeyViolation. Because that is an IntegrityError
(not a ValueError) the worker framework's
detect_scan_failures path does not mark the scan
FAILED — the SQS message just gets retried forever and the scan stays
IN_PROGRESS. Symptom: a scan stuck on the resolver stage
with repeating STARTED → COMPLETED pairs but no
RUNTIME_PATH_COMPLETED.
What it does: reads all system objects from the selected source,
compares against the local object table, and inserts only the
missing ones (ON CONFLICT (id) DO NOTHING). Idempotent — safe to
re-run any time. Total volume is tiny (≈7 rows today), so this is fast and cheap.
Kubernetes resources for this namespace. Pods moved to Home where they matter most.
Deployments
| Name | Ready | Image | Age | |
|---|---|---|---|---|
| Loading... | ||||
ScaledJobs (Pipeline Workers)
| Name | Min | Max | Paused | Queue | Image | Age |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Rare / destructive operations and pipeline internals. Most developers never need these.
ArgoCD App Overrides
HEAD (main).
Reinitialize Database
Drops all tables in this environment's database, recreates schema + extensions, runs DB migrations, and applies baseline seed data (accounts, system users, reference catalogs). Then copies all pensa_internal users and their permissions from production so every Pensa developer can log in immediately (idempotent — safe to re-run). Use when the database is corrupted or you want a clean slate.
Export / Import Database
Export: downloads a pg_dump SQL snapshot of the current database — use as seed data or share with colleagues.
Import: upload a previously exported .sql file to restore a database state.