docs: fixing the log file path for Langflow Desktop

[andifilhohub]

Updated the documentation to reflect the correct location of the Langflow Desktop logs. The previous path was outdated — the logs were only found at the new directory indicated in this update.

Summary by CodeRabbit

• Documentation
  • Updated the Windows log file location for Langflow Desktop. Logs are now stored in the local AppData logs directory instead of the roaming AppData cache location. Updated example commands reflect the new path.

[coderabbitai]

Walkthrough

The PR updates documentation for Langflow Desktop log file paths on Windows, changing from a roaming AppData cache directory to a local AppData logs directory, with corresponding example command updates.

Changes

Cohort / File(s)	Summary
Documentation path updates docs/docs/Develop/logging.mdx	Updated Windows log path from Roaming AppData cache location to local AppData logs directory and refreshed example command sequences accordingly

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single file with purely cosmetic path/location updates
• No logic, error handling, or structural changes introduced

Possibly related PRs

• docs: update LF Desktop logging path #10089: Also modifies docs/docs/Develop/logging.mdx to update Langflow Desktop log paths, though selecting a different Windows path variant

Suggested labels

documentation, lgtm

Suggested reviewers

• italojohnny
• Cristhianzl

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 2 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Test File Naming And Structure	❓ Inconclusive	This pull request is a documentation-only change that modifies the Windows log file path documentation in docs/docs/Develop/logging.mdx. The custom check requires verification of test file naming and structure across backend tests (test_*.py), frontend tests (*.test.ts/tsx), integration tests, and related test conventions. Since this PR contains no test files of any kind—only documentation updates—the check criteria cannot be evaluated against the actual changes in this PR.	The test file naming and structure check is not applicable to documentation-only pull requests. If this check is intended to validate all PRs, it should be scoped to only verify PRs that actually contain test files or code changes. For documentation-only changes like this one, consider either skipping this check or clarifying that it applies only to code-related submissions.
Excessive Mock Usage Warning	❓ Inconclusive	This pull request is a documentation-only update that modifies docs/docs/Develop/logging.mdx to correct the Windows log file path for Langflow Desktop. The changes consist exclusively of path/location updates within markdown documentation with no modifications to test files, test code, mocks, or application source code. The "Excessive Mock Usage Warning" check is designed to identify poor test design patterns through excessive mock usage, which is not applicable to documentation changes. No test files are included in this PR's modifications.	The custom check for "Excessive Mock Usage Warning" cannot be meaningfully applied to this PR because it contains no test files or code modifications. This check is designed for source code and test file analysis, not documentation updates. Consider configuring the check to skip documentation-only PRs, or clarify the check scope if it should apply to all PR types. For this specific PR, documentation updates do not require mock usage evaluation.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "docs: fixing the log file path for Langflow Desktop" is directly related to the main change in the changeset. The raw summary confirms that the PR updates the Windows path for Langflow Desktop logs and the example command sequences, while the PR objectives state that documentation was updated to reflect the correct location of Langflow Desktop logs. The title is concise, clear, and specific enough that a teammate scanning the history would understand this is a documentation update addressing an outdated log file path for Langflow Desktop. It avoids vague terms and clearly conveys the primary change.
Test Coverage For New Implementations	✅ Passed	This PR contains only documentation updates to the logging.mdx file, changing Windows log file paths from the Roaming AppData cache location to the Local AppData logs directory. No code has been added, modified, or implemented. The custom check for test coverage is designed for code changes (new functionality, bug fixes, new features) and requires corresponding tests. Since this PR is purely documentation-only with no code implementation or logic changes, the test coverage requirements do not apply.
Test Quality And Coverage	✅ Passed	This pull request is a documentation-only change that updates the Windows path for Langflow Desktop logs in the docs/docs/Develop/logging.mdx file. According to the provided summary, all changes are purely path/location updates with no new logic or error handling introduced. Since the custom check is designed to evaluate "the quality and comprehensiveness of tests for new implementations," and this PR does not introduce any new code implementations or business logic, there are no tests required or expected for this change. The check criteria for testing async functions, validating behavior, following testing patterns, and testing API endpoints are not applicable to documentation updates.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e24c387 and f6ded5e.

📒 Files selected for processing (1)

• docs/docs/Develop/logging.mdx (2 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/docs_development.mdc)

docs/**/*.{md,mdx}: All Markdown/MDX pages must start with front matter including at least title and description; include sidebar_position for docs pages when applicable
Code blocks must specify a language and may include a title (```lang title="…")
Use sentence case for headings and keep paragraphs short and scannable
Write in second person, present tense, with a professional but approachable tone
Use inline code with backticks for code terms; use bold for UI elements and italics for emphasis; keep lists in parallel structure
Ensure internal links are functional and navigation works (update cross-references as needed)
Verify all code examples in docs and blog actually run as shown
Use correct terminology capitalization: Langflow, Component, Flow, API, JSON
Reference images with absolute paths under /img/... and provide descriptive alt text

Files:

• docs/docs/Develop/logging.mdx

docs/docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/docs_development.mdc)

Use Docusaurus admonitions (:::+tip|warning|danger) instead of custom callouts in docs pages

Files:

• docs/docs/Develop/logging.mdx

🧠 Learnings (3)

📚 Learning: 2025-08-07T20:23:23.569Z

Learnt from: edwinjosechittilappilly
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-08-07T20:23:23.569Z
Learning: Some Langflow starter project files and components still use `from loguru import logger` instead of the centralized structlog logger from `langflow.logging.logger`. These should be updated to ensure consistent structured logging across the entire codebase.

Applied to files:

• docs/docs/Develop/logging.mdx

📚 Learning: 2025-08-07T20:23:23.569Z

Learnt from: edwinjosechittilappilly
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-08-07T20:23:23.569Z
Learning: The Langflow codebase has an excellent structlog implementation that follows best practices, with proper global configuration, environment-based output formatting, and widespread adoption across components. The main cleanup needed is updating starter project templates and documentation examples that still contain legacy `from loguru import logger` imports.

Applied to files:

• docs/docs/Develop/logging.mdx

📚 Learning: 2025-08-07T20:23:23.569Z

Learnt from: edwinjosechittilappilly
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-08-07T20:23:23.569Z
Learning: The Langflow codebase uses structlog for structured logging with a centralized configuration in `src/backend/base/langflow/logging/logger.py`. The configuration supports multiple output formats (JSON, CSV, console) based on environment settings and properly implements global log level filtering.

Applied to files:

• docs/docs/Develop/logging.mdx

🔇 Additional comments (2)

docs/docs/Develop/logging.mdx (2)

1-4: Front matter is complete and properly formatted.

The document starts with required front matter including title and slug, following Docusaurus conventions.

---

24-24: Updated Windows log paths are consistent across first two examples.

Both line 24 (path listing) and line 64 (cd example) correctly reflect the new Windows log location in AppData\Local\...\logs.

Also applies to: 64-64

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mendonk]

Tagging @Cristhianzl for review as the windows expert

[Cristhianzl]

lgtm

[mendonk]

Approving for docs with @Cristhianzl for eng review

[mendonk]

Thanks @andifilhohub