---
id: troubleshooting.expert-contributions
title: Expert Contribution problems
summary: Diagnose contribution access, task routing, checkpoint, synchronization, completion, and artifact-reconciliation problems.
kind: error
product_area: troubleshooting
status: stable
updated: 2026-08-22
canonical: /docs/troubleshooting/expert-contributions
---

# Expert Contribution problems

## Symptom

An expert cannot open the Contribution, reaches the wrong task, sees stale work, cannot submit a response, remains at a checkpoint or waiting state, or completes the experience without the administrator seeing reconciled evidence.

## Likely causes

- The expert lacks access or opened a link for a different Contribution.
- The task handoff changed and the browser still points to an earlier route.
- A form, chat, interview, or case-review command has not synchronized.
- The task lease, realtime connection, or retry state needs recovery.
- A checkpoint still requires confirmation or correction.
- The expert experience is complete, but contributed artifacts have not yet been reconciled in the administrator workspace.
- The Contribution was cancelled or changed while the expert was working.

## Fix

1. Confirm the Contribution identity and expert assignment in **Expert Contributions → Contributions**.
2. Inspect its current status and task plan rather than relying on the expert's previous URL.
3. Ask the expert to reopen the Contribution entry route so the current task handoff can resolve.
4. If the UI shows a waiting, retry, or synchronization state, follow that state and avoid duplicate submissions.
5. Inspect checkpoints for an unconfirmed or corrected statement.
6. Use **Logs & Status** to distinguish expert completion from reconciliation or artifact-materialization work.
7. Check **Contributed Artifacts** and the owning Correctness Governance, Assets, or Coverage Management surface before concluding that accepted material is missing.

## Prevention

- Keep Contribution objectives and task sequences narrow.
- Verify expert access before sending the request.
- Preserve checkpoints for consequential meaning.
- Use the current Contribution entry route instead of bookmarking an internal task route.
- Teach administrators that task completion, evidence reconciliation, and artifact governance are separate transitions.
- Avoid submitting the same response repeatedly when the product shows a pending or retryable synchronization state.

{% example-demo title="Example: completed task but missing policy" %}
An expert completes the final checkpoint, but the policy does not yet appear in Correctness Governance. Logs & Status shows that the Contribution is complete while evidence reconciliation remains active. The administrator waits for reconciliation, then inspects Contributed Artifacts and materializes the policy through its owning workflow instead of asking the expert to repeat the task.
{% /example-demo %}

## Related task pages

{% related-card-grid title="Related task pages" %}
- [Request an Expert Contribution](/docs/expert-contributions/request-contribution)
- [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution)
- [Product quickstart](/docs/quickstart)
{% /related-card-grid %}

## Related reference pages

{% related-card-grid title="Related reference pages" %}
- [Expert Contributions](/docs/expert-contributions)
- [Contributed Artifacts](/docs/expert-contributions/contributed-artifacts)
- [Roles and permissions](/docs/reference/permissions)
{% /related-card-grid %}

## Source confidence

Code-backed: the expert routes, contribution runtime, durable command synchronization, and administrator status surfaces support these diagnostic boundaries.