Add troubleshooting to failure computed assets

[shindiogawa]

No description provided.

[greptile-apps]

Greptile Summary

This PR extends the Unloadable Container Error documentation to cover computed assets (Computed Tables, Computed Files, Computed Joins), which cannot be reset via a Sync operation and instead require a forced Edit → Validate → Save cycle.

• scan.md gains a second resolution path for computed assets alongside the existing Sync-based path for tables/views/file patterns; the Cause and tip sections are updated to match.
• profile.md receives a new Troubleshooting section mirroring the scan.md guidance; authored-check.md and container/overview.md get inline callouts pointing to the full resolution steps.

Confidence Score: 4/5

Safe to merge — all changes are documentation only with no code logic affected.

Step 4 of the tables/views resolution path still tells users to 'run the scan operation again' even though the section intro now covers profiles and check validations too; a user who hit the error during a profile run could be momentarily confused. Everything else — link targets, anchor names, relative paths — checks out correctly across all five files.

docs/operations/scan/scan.md — the tables/views resolution step 4 wording is slightly out of sync with the broadened section introduction.

Important Files Changed

Filename	Overview
docs/operations/scan/scan.md	Expanded Unloadable Container Error section to cover computed assets alongside tables/views/file patterns; step 4 in the tables/views path still says 'Run the scan operation again' even though the section heading was broadened to include profiles and check validations.
docs/operations/profile/profile.md	New Troubleshooting section added at the end with the Unloadable Container Error sub-section; links and relative paths to sync.md and scan.md are correct.
docs/operations/sync/sync.md	Tip callout expanded to distinguish Sync-resolvable containers from computed assets and links to the full resolution steps; content is accurate and paths are correct.
docs/data-quality-checks/authored-check.md	Added a note callout after the failed-validation screenshot explaining the Unloadable Container error and how to resolve it for both container types; links and relative paths are valid.
docs/container/overview.md	Inline resolution hint added to the existing Unloadable note, summarising the two-path fix alongside the existing link; target="_blank" preserved from the original link.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Container marked Unloadable\n3 consecutive failures] --> B{Container type?}
    B -->|Table / View / File pattern| C[Run Sync Operation\non the datastore]
    B -->|Computed asset\nComputed Table / File / Join| D[Open asset → click Edit]
    C --> E{Sync successful?}
    D --> F[Fix SQL if needed\nor re-save as-is]
    F --> G[Click Validate]
    G --> H{Validation passes?}
    H -->|Yes| I[Click Save →\nUnloadable status cleared]
    H -->|No| J[Fix root cause\ne.g. renamed column, dropped table]
    J --> G
    E -->|Yes| K[Re-run scan / profile /\ncheck validation]
    E -->|No| L[Investigate root cause\npermissions, schema, network]
    I --> K
    K --> M[Container processes normally]

Loading

_{Reviews (1): Last reviewed commit: "Add troubleshooting to failure computed ..." | Re-trigger Greptile}

[greptile-apps]

Step 4 still only says "Run the scan operation again", but the section intro was broadened to cover profiles and quality-check validations as well. A user who first hit this error during a profile run would find the instruction misleading.

Suggested change

	4. Run the scan operation again. The previously unloadable container should now be processed normally.
	4. Re-run the operation that surfaced the error (scan, profile, or check validation). The previously unloadable container should now be processed normally.