Skip to content
D
Documentation

Troubleshoot Entity and Flow Problems

page
6 min readUpdated

This page helps you resolve common problems with missing entities, relationships, source symbols, and captured flows. Use these checks to confirm that you are viewing the right information and to identify when an item needs attention.

Overview

Source Intelligence helps you explore the entities and flows identified in your project. Entities can represent items such as components, hooks, pages, layouts, routes, contexts, providers, stores, controllers, services, repositories, and middleware. Flows show how related parts work together, such as user journeys, authentication sequences, and pipeline activity.

You may need this page when an expected entity does not appear in the entity list, a relationship is unclear or missing, the View Source option does not show the source information you expect, or a captured flow is not visible. For example, you might be looking for an Authentication Flow, an OAuth 2.0 Flow, or a relationship where one component renders another component.

Use the entity search and flow filters first. Then use the available source view and resolution controls to investigate the item further.

📷 Screenshot pending: Entity list showing the Search entities… field, an entity selection, and the View Source action.

Prerequisites

Before you begin, make sure that:

  • You have opened the correct project.
  • You know the approximate name of the missing entity or flow.
  • You can access the entity list and captured flows for the project.
  • You have permission to view the relevant project source information.
  • You understand whether you are looking for an entity, a relationship, or a flow.
  • You have allowed any current analysis or capture activity to finish before checking results.

Step-by-Step Instructions

  1. Open the entity list for your project.

    Start from the project’s technical documentation area and open the entity list. Look for the search field labeled Search entities… or Search entities....

    If you are searching for a known item, enter part of its name. For example, search for Authentication, OAuth, User Flow, or Help Widget.

  2. Check whether the entity appears under a different type or name.

    Entity names may be grouped according to their role. Common entity types include:

    • COMPONENT
    • HOOK
    • PAGE
    • LAYOUT
    • ROUTE
    • CONTEXT
    • PROVIDER
    • STORE
    • CONTROLLER
    • SERVICE
    • REPOSITORY
    • MIDDLEWARE

    For example, an expected UI element may appear as a component, while supporting behavior may appear as a hook, provider, or service. Search with a shorter term if an exact name does not return a result.

  3. Select the entity and inspect its details.

    Select the matching item from the results. The details area may be identified as Entity Detail. Review the entity’s displayed relationships to understand how it connects to other items.

    Relationship descriptions can indicate actions such as one component renders another component or a component uses a hook. If you expected a direct connection but see an intermediate entity, inspect that intermediate entity before concluding that the relationship is missing.

  4. Use source view to verify a source symbol.

    Select View Source for the entity you are investigating. In the source area, use the available display choice to switch between Source and any comparison view that is available.

    Confirm that the displayed source content corresponds to the entity you selected. If the source view is not what you expected, return to the entity list and verify that you selected the correct entity with a similar name.

    📷 Screenshot pending: Source view with the View Source action and the Source display option.

  5. Check the entity’s resolution state.

    Look for the Resolve action and the status summary such as 4 All Resolved. A resolved status indicates that the listed items have been addressed; it does not necessarily mean every possible entity or relationship is present.

    If an item remains unresolved, select it and review the available details and source view before marking it resolved.

  6. Open captured flows and choose the appropriate flow group.

    In the captured flows area, use the available flow options, such as Loop Flows, Pipeline Flows, and User Flow.

    Look for the flow that best matches your task. Examples may include:

    • 🔐 Authentication & Authorization Flow
    • OAuth 2.0 Flow
    • Authorization Code Flow
    • Authentication Flow
    • Agent Loop Flow Diagrams
    • Evolved Pipeline Flow
    • 🛟 Atloria Help Widget

    If a flow is not visible in one group, check the other flow options before assuming it was not captured.

  7. Recheck the flow from the relevant entity.

    When a flow appears incomplete, return to the associated entity and inspect its relationships. A flow may span several entities, such as a page, component, hook, provider, service, and repository. Checking each related entity can reveal where the displayed path changes or stops.

    📷 Screenshot pending: Captured flows area showing Loop Flows, Pipeline Flows, and User Flow options.

Tips and Best Practices

  • Search using distinctive keywords rather than full names. For example, use Authorization instead of entering a complete flow title.
  • Check both entity types and relationships. An item that seems missing as a component may be represented as a hook, route, service, or provider.
  • Treat relationship wording carefully. Renders and uses describe different connections, so they may lead you to different entities.
  • Use View Source to validate the selected entity before acting on a suspected missing symbol.
  • Review all available flow groups—Loop Flows, Pipeline Flows, and User Flow—when looking for captured activity.
  • Do not use Resolve simply to remove an item from your attention. Resolve it after you have verified the entity, relationship, or flow information.

Troubleshooting

Problem: You cannot find an expected component, hook, page, service, or other entity in Search entities….

Cause: The entity may use a different displayed name, may be categorized under another entity type, or may be represented by a related item rather than the name you expect.

Solution: Search using a shorter or distinctive keyword. Then check related types such as COMPONENT, HOOK, PAGE, ROUTE, CONTEXT, or SERVICE. Select likely matches and review Entity Detail and relationships.

A relationship appears to be missing

Problem: You expect one entity to connect directly to another, but the relationship is not shown.

Cause: The connection may be indirect. For example, a component can render another component through an intermediate entity, or it can use a hook that leads to additional related entities.

Solution: Open the first entity, review its displayed relationships, and follow each related entity in sequence. Look for relationship wording such as renders and uses. Use View Source to confirm that you are investigating the intended entity.

A source symbol or flow is not visible

Problem: View Source does not show the expected source information, or a flow such as Authentication Flow is not listed.

Cause: You may have selected a similarly named entity, chosen the wrong source display option, or checked only one flow group.

Solution: Return to Search entities… and select the correct entity. Open View Source, confirm the Source display option, and then check Loop Flows, Pipeline Flows, and User Flow for the missing flow.

Was this page helpful?

Download as PDF
ADocs generated by Atloria — from the code, always in sync →
Troubleshoot Entity and Flow Problems — Atloria (self dogfood)