Context Engine Audit and Troubleshooting
Context Engine audit explains what happened during indexing, vault refresh, graph, and context retrieval activity.
Where to Look
Section titled “Where to Look”| Deployment mode | Where to inspect |
|---|---|
| Cloud Hosted | Customer controller, Cloud Audit, Context Engine audit tab where enabled. |
| Self Hosted | Local Worker UI Context Engine audit pages where configured. |
If the workspace does not show Context Engine audit, confirm feature availability and plan gates with MergeLoom.
Audit Event Details
Section titled “Audit Event Details”An audit detail can include:
- event ID
- event type
- status
- provider/model where relevant
- input and output token counts where available
- cost estimate where available
- repositories included
- progress timeline
- error or failure messages
Cloud audit views should use safe metadata and summaries rather than raw source dumps.
Common Issues
Section titled “Common Issues”Cloud Context Engine Is Not Ready
Section titled “Cloud Context Engine Is Not Ready”Check:
- workspace is Cloud Hosted
- email is verified
- payment method is verified if required
- cloud runtime status is ready
- Cloud AI credits are available
- plan allows the requested operation
Self Hosted Context Engine Is Not Ready
Section titled “Self Hosted Context Engine Is Not Ready”Check:
- Context Engine service URL
- worker token and internal token
- network path from worker to Context Engine service
- provider readiness for AI-assisted indexing
- local storage or database configuration
- worker health page
Indexing Is Too Expensive or Too Large
Section titled “Indexing Is Too Expensive or Too Large”Check:
- repository count
- include patterns
- exclude patterns
- generated folders
- dependency directories
- vendored code
- binary or large files
Start with a smaller repository scope.
Vault Refresh Shows Stale Context
Section titled “Vault Refresh Shows Stale Context”Check:
- latest index status
- vault refresh status
- selected repositories
- whether documentation sources changed outside the indexed scope
- whether a failed or paused indexing run needs attention
Context Is Not Used in a Run
Section titled “Context Is Not Used in a Run”Check:
- Context Engine is enabled for the workspace
- selected work repository is authorized
- context source applies to the selected work repository
- job audit shows Context Engine or context-pack activity
- ticket directives did not select a different work/context scope
Related pages: