Document the search rules fuel environment variables

[qdequele]

Description

v1.50 introduced the "DSR fuel" system as part of scaling search rules to 75,000 rules. It exposes four environment variables that bound how much work rule resolution may spend during a search. The changelog mentions "configurable limits via environment variables" without naming them, and none appeared in the configuration reference.

Added a grouped ### Search rules fuel section following the same structure as the existing ### S3 options group, with one #### entry per variable:

Variable	Default	Max
MEILI_EXPERIMENTAL_DSR_FUEL_MAX_COUNTED_WORDS	10	255
MEILI_EXPERIMENTAL_DSR_FUEL_MAX_ACTIVE_RULES	1000	4294967295
MEILI_EXPERIMENTAL_DSR_FUEL_MAX_PIN_ACTIONS	100	4294967295
MEILI_EXPERIMENTAL_DSR_FUEL_WORD_FUEL	4096	4294967295

Names, defaults, maxima and semantics come from the v1.50.0 release notes (engine PRs #6484 and #6506), not from the changelog entry.

Placed with the other search-related experimental options rather than the task queue ones, which also keeps it clear of #3656's insertion point in the same file.

npm run check-broken-links passes.

Checklist

For internal Meilisearch team member only:

• I checked and followed our internal guidelines
• ⚠️ I updated the code samples according to our internal guidelines (no code sample changes needed)

For external maintainers

• Did you use any AI tool while implementing this PR? Yes. Claude Code found the gap auditing docs against the changelog, read the variable names and limits from the release notes, and drafted the section.
• Have you made sure that the title is accurate and descriptive of the changes?

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
meilisearch-documentation	🟢 Ready	View Preview	Aug 18, 2026, 3:08 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[coderabbitai]

Warning

Review limit reached

@qdequele, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 minutes

Limit details: You’ve used all 2 included reviews currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cb976dac-5b76-4487-be11-f5df4d718bf8

📥 Commits

Reviewing files that changed from the base of the PR and between 00893a4 and 493118a.

📒 Files selected for processing (1)

• resources/self_hosting/configuration/reference.mdx

---

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.}

[qdequele]

@dureuill you introduced the DSR fuel system in meilisearch#6484 and meilisearch#6506, so tagging you for review.

I took the four variable names, defaults and maxima from the v1.50.0 release notes, and wrote one-line explanations of what each budget bounds. The semantics of WORD_FUEL versus MAX_COUNTED_WORDS are the pair I am least sure I have distinguished clearly, since both relate to conditions.query.words.

I also wrote that the defaults suit most rule sets and that raising a limit is only worthwhile once you have confirmed a specific budget is the cause of rules not applying. If there is a better diagnostic signal for that, it would be a useful addition.

[dureuill]

If there is a better diagnostic signal for that, it would be a useful addition.

not yet, but to keep in mind once we add a "preview/test/explain" mode for rule activation