Intake Requests - Assessment phase - Bedrock KB Insertion Failure and Status Mismatch

[Srividhyavenugopa]

Document used

GlobalBuild-AP-Exception-Handling-Business-Overview.md

A document upload initially appears as Failed in the UI, then transitions to Ready after a short delay, while KB insertion for the same document path remains FAILED. Because insertion does not complete successfully, the downstream assessment auto-trigger does not run.

Impact

• Users receive conflicting status signals (Failed then Ready).
• The workflow cannot progress to assessment when KB insertion fails.

Observed Behavior

1. Upload initiated from app UI.
2. UI shows indexing failure (Indexing failed: FAILED).
3. After a few seconds, document shows Ready state.
4. Assessment/design/planning/build phases do not auto-trigger because KB insertion did not succeed.
5. S3 object is present in bucket/prefix.
6. KB insertion row remains FAILED.

Reproduction Steps

1. Configure KB data source and upload pipeline.
2. Upload markdown document (example above).
3. Observe initial UI failure for indexing.
4. Wait several seconds and refresh status.
5. Observe document becoming Ready while KB row indicates FAILED.

Attachments

• Screenshot: upload modal showing Indexing failed: FAILED
• Screenshot: S3 object exists for uploaded file
• Screenshot: KB document list showing FAILED

Business Context (Optional)

This issue was discovered during a Slalom-led enterprise pilot showcasing advanced, event-driven agentic workflows. We are working to ensure robust and deterministic behavior before broader rollout.