wdevs/amcs
5
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Add operational checks and visibility for background metadata/embedding processing #28

New Issue
Closed
opened 2026-04-13 20:13:46 +00:00 by sgcommand · 0 comments
sgcommand commented 2026-04-13 20:13:46 +00:00
Member
Copy Link

Problem

Background enrichment only works if operators can tell whether metadata extraction and embedding generation are keeping up. Current visibility into pending, failed, and retried background work appears limited.

Impact

  • Silent backlog growth
  • Failed enrichment can go unnoticed
  • Hard to distinguish transient AI/provider issues from stuck records

Expected behavior

AMCS should expose operational checks for background metadata and embedding processing so failures and backlogs are visible before users notice degraded behavior.

Acceptance criteria

  • There is a recurring operational check or report for pending/failed metadata and embedding work
  • Logs or metrics expose backlog size, retry counts, and recent failure reasons
  • Missing embeddings continue to degrade gracefully in user-facing flows
  • Operators can tell whether background workers are healthy without manual database inspection
  • Documentation identifies how and where the background checks run
## Problem Background enrichment only works if operators can tell whether metadata extraction and embedding generation are keeping up. Current visibility into pending, failed, and retried background work appears limited. ## Impact - Silent backlog growth - Failed enrichment can go unnoticed - Hard to distinguish transient AI/provider issues from stuck records ## Expected behavior AMCS should expose operational checks for background metadata and embedding processing so failures and backlogs are visible before users notice degraded behavior. ## Acceptance criteria - There is a recurring operational check or report for pending/failed metadata and embedding work - Logs or metrics expose backlog size, retry counts, and recent failure reasons - Missing embeddings continue to degrade gracefully in user-facing flows - Operators can tell whether background workers are healthy without manual database inspection - Documentation identifies how and where the background checks run
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
debugging
integration
planned
ux
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hein root sam sgcommand warkanum
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/amcs#28
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?