Skip to content

Conversation

@runllm-pr-agent
Copy link

We have updated the documentation based on the following suggestions:

Log Limits per Session

  • Info and Warning Logs: The default limit is set to 100 logs per session.
  • Error Logs: A higher limit of 250 logs per session is allowed to accommodate more critical information.

If you encounter the message [Embrace]: Warning Log limit has been reached, it indicates that the maximum number of logs for a given category has been exceeded within a single session. For use cases requiring more logs, please contact support to discuss your needs, which may include recommendations for alternative solutions such as using breadcrumbs.

@runllm-pr-agent runllm-pr-agent bot requested review from a team as code owners August 21, 2025 17:09
@github-actions
Copy link

github-actions bot commented Aug 21, 2025

Summary - Markdown Lint

Rule     Violations   Fixable  Percentage
--------------------------------------------------
MD022    1            1         100.0%
--------------------------------------------------
Total    1            1         100.0%

You can find an explanation of all linting rules here.

Run rumdl check locally, use --fix to fix issues automatically where possible.

@github-actions
Copy link

github-actions bot commented Aug 21, 2025

Summary - Link Checker

Status Count
🔍 Total 418
✅ Successful 338
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 80
❓ Unknown 0
🚫 Errors 0
Full Github Actions output


- Maximum number of error logs per session: 500
- Maximum number of warning logs per session: 200
- Maximum number of error logs per session: 250
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these values are incorrect for web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants