> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/menu-areas/help-and-node/troubleshooting.md).

# Troubleshooting

Start with the message on the current page. It usually names the missing field, permission, record state, or action. Use the steps below when you need more help.

## I cannot see a menu item

{% stepper %}
{% step %}

## Select the correct workspace

Select **Operations & workspaces → Choose workspace**. Check that you opened the correct workspace.
{% endstep %}

{% step %}

## Check your membership

Check that your membership is active and has not expired.
{% endstep %}

{% step %}

## Check your role and permission

Ask a workspace Manager to check your role and permission. Some areas also need a professional role, appointment, or separate approval.
{% endstep %}

{% step %}

## Check enabled features

Check the workspace's enabled features in **People & settings → Workspace settings**. A feature choice can hide an area.
{% endstep %}

{% step %}

## Check handling access

Check your handling access. A page can be visible while a protected record is not.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Do not treat an absent menu item as proof that no records exist. The menu shows only the pages available to your current account and workspace.
{% endhint %}

## Search did not change the list

Enter the terms in the search field. Then select its **Search**, **Find**, or other named action. Typing in a field does not always run the search. Check active filters and the current page of results. Use **Clear all filters** where the page provides it.

## A save failed

{% stepper %}
{% step %}

## Read the error

Read the error or missing-input list on the page.
{% endstep %}

{% step %}

## Check required fields

Check each required field. Check dates, handling, and the reason for a change.
{% endstep %}

{% step %}

## Check node connectivity

Check that your browser can reach the CORTEX node. **Help & node → Node & capabilities** explains connection and save behavior.
{% endstep %}

{% step %}

## Refresh the record

Open or refresh the exact record. Another person may have saved a newer version.
{% endstep %}

{% step %}

## Check whether the action already saved

Check whether your first action saved before you select the action again. Do not create a duplicate to test a failed response.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The node keeps only a save that it confirms. A browser has no automatic offline queue for CORTEX changes.
{% endhint %}

## I cannot make a requirement Active

Open **Intelligence cycle → Direction** and open the requirement. Check that its decision point and required details are present. In **Change status**, select a valid next state, give the reason, and select **Update status**. The page shows missing prerequisites. A new requirement or owner assignment does not start collection by itself.

## I cannot use a source or acquire material

Open **Sources & evidence → Sources** and check the source state. Check the authority that applies to this source, this requirement, and this use. A new authority case may need review before collection. For an upload, use **Sources & evidence → Evidence memory → Acquire material**. Select a visible requirement and an active source, then check the original file and acquisition details. The material must pass its separate scan and processing steps before you cite a passage.

## I cannot add an evidence citation

Check that the original material has a ready processing version. Select the exact segment and range. Review an interpretation or translation when one applies. Select **Preview quotation** before **Add this evidence citation**. Check handling and source access if the material is absent from the picker.

## A product cannot be released

Open **Intelligence cycle → Products** and inspect the exact product revision. Check its evidence, review state, and handling. Then open **Release & sharing → Releases**. The release has its own review, approval, and publication steps. A draft, export, derivative, or download is not a release. The page names the missing approval or permission.

## A recipient has not acknowledged a package

Check the exact package in **Release & sharing → UK recipient packages** or **Received UK packages**, according to your role. A notice, delivery, acknowledgement, and feedback are separate retained actions. The recipient can record receipt; the requirement owner decides whether that response answers the question. Do not infer acknowledgement from an opened page.

## The node says Offline

**Help & node → Node & capabilities** describes node connectivity. A node can continue approved local work when its external connection is unavailable. The browser still needs a connection to the node to save. Hosted generation and external feeds can be unavailable while local functions remain available. Read the current status and reason before you retry.