> ## Documentation Index > Fetch the complete documentation index at: https://docs.flowx.ai/llms.txt > Use this file to discover all available pages before exploring further. # Checking a version for issues > Validate the resources in a project version from the Issues Console, see where each problem is, and review what is outstanding before you commit. ## Overview The Designer can check the resources in your project version and list what it finds in one place. Findings are listed in the **Issues Console**, and marked where they occur so you can go straight to them. Open the console from the **Issues** button in the bottom bar of the project, which shows how many findings the version has. That count covers every finding in the version, whatever filters you apply in the console. The console is a floating window. Drag it by its title bar, resize it from any edge or corner, and close it with the close button. It belongs to the project rather than to a single page, so it stays open, at the same size and position, as you move between the project's pages. > [!NOTE] > > **What is validated.** Processes, UI Flows and integration workflows are checked. Other resource types are listed as not validated rather than reported as clean, so an empty result never means more than it should. ![The Issues Console floating over the Processes list, set to All in version and grouped by Severity. Three errors report missing Web and Mobile entry points and a swimlane that references a role outside the project version; six warnings report workflow nodes that are not reachable from the START node. The filter row shows the Show, Search and Group controls and error, warning and info count chips, and the bottom bar shows 9 Issues, checked just now.](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/issues-console.png) > [!NOTE] > > In the workflow editor, the console also has a **Run Logs** tab for the workflow's test runs. *** ## Running a check A version that has been checked before opens with the results of its last check, whoever ran it. A version that has never been checked shows **Nothing checked yet. Run a check to validate every resource in this version.** and a **Check for issues** button. To check again, select the refresh button next to the **Issues** count in the bottom bar, or in the console's title bar. Both places show how long ago the last check ran, for example `5 min ago`, so you can tell a current result from a stale one. > [!TIP] > > Run a check again after a round of edits. The list describes the version as it was at the last check, not as it is now. *** ## Reading the list Every finding is reported at one of three severities, **error**, **warning**, or **info**, and names the element and the resource it came from. Select that name to go straight to the element. Hover over a finding to show its lightbulb button. Select it to expand a **Suggested Fix** with the remediation and a **Go to** button that opens the element. The filter row above the list narrows what you see: | Control | What it does | | - | - | | **Show** | Choose **In context** to see only the findings for the page you are on (a resource list, a single resource, or the version settings), or **All in version** for everything. **In context** is the default on pages that have one. A choice you make lasts until you move to another page. | | Severity chips | One chip each for errors, warnings, and info, showing the count. Turn any of them off. All three are on by default. | | **Search** | Filter by text in the message, the resource name, or the element name. | | **Group** | **Severity**, **Resource**, or **None**. Grouping by severity is the default, and each group can be collapsed. | Your severity and grouping choices are remembered in your browser, across versions. Search is not. *** ## Which version settings does a check cover? Besides resources, a check covers the version's own settings and its library dependencies. Selecting one of these findings opens the page where you fix it: entry point and theme findings open the version settings, and dependency findings open the **Dependencies** page. | Rule | Severity | Reported when | | - | - | - | | **Missing entry point** | Error | The version has no entry point for a channel (Web or Mobile), so it can't be launched there. | | **Broken entry point** | Error | A channel's entry point references a process or UI Flow that no longer exists. | | **Entry point platform mismatch** | Warning | A channel's entry point is a resource built only for the other platform. | | **Broken theme reference** | Error | The version references a theme that isn't in this workspace. Renderers fall back to a FlowX built-in theme. | | **Missing library build** | Error | The version depends on a library build that isn't in this workspace. Nothing from that library can run until the build is imported. | | **Missing transitive library build** | Error | A library the version depends on needs a build of another library that isn't in this workspace. | | **Unused dependency** | Info | The version depends on a library but uses none of its resources. The dependency still brings its own dependencies into the version. | *** ## Markers Findings are also marked where they live: on workflow list rows, on the page title, and on nodes in the workflow canvas. Markers show errors and warnings only, never info, and the page title marks errors only. Selecting a marker opens the Issues Console; on a canvas node, it also focuses that node. To turn markers off, open the settings popover in the filter row and clear **Show on canvas and lists**. The console keeps working; only the markers elsewhere are hidden. ![Workflow canvas with an error marker on the computeQuote node header and on the page title, and a warning marker on applyDiscount, a node not connected to the flow. The bottom bar shows Run Logs, the 11 Issues count and the time of the last check.](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/issues-console-canvas-markers.png) *** ## Before you commit Opening **Commit Changes** runs a check on its own, and each changed resource in the modal shows what the check found: its errors and warnings, a check mark when it has no issues, or a minus sign when its type is not validated yet. A resource you are deleting is shown as not validated, since it is not part of the version being described. Above the commit button, a summary reads **Issues found** or **No issues found** for the changed resources. > [!WARNING] > > **Findings do not block the commit.** When changed resources have errors, the button reads **Commit with 2 errors** (with the actual count), but you can still commit. Treat the list as a review step you perform, not a gate the Designer applies for you. ![Commit Changes modal listing three changed resources: a UI Flow and a workflow with check marks, and the calculateShippingQuote workflow with one error and one warning. An Issues found summary sits above the buttons, and the commit button reads Commit with 1 error.](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/issues-console-commit-modal.png) *** ## Related resources > [card] [Versioning](https://docs.flowx.ai/6.x/docs/projects/managing-applications/versioning.md) > > Project versions, committing changes, branches and builds > [card] [Integration Designer](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/integration-designer.md) > > Building the workflows this check validates ## Related topics - [FlowX.AI 5.12.0 Release Notes](https://docs.flowx.ai/release-notes/v5.x/v5.12.0-september-2026/v5.12.0-september-2026.md) - [Versioning](https://docs.flowx.ai/6.x/docs/projects/managing-applications/versioning.md) - [FlowX.AI 6.0.0 Release Notes](https://docs.flowx.ai/release-notes/v6.x/v6.0.0-october-2026/v6.0.0-october-2026.md) - [Dynamic & computed values](https://docs.flowx.ai/6.x/docs/building-blocks/ui-designer/dynamic-and-computed-values.md) - [FlowX.AI Designer](https://docs.flowx.ai/6.x/docs/flowx-designer/overview.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.