docs: link recursive functions guide from trace rate limit troublesho…

[monicakh]

Documentation

• Added reference to the "Recursive Functions — What gets rate limited" guide in troubleshooting documentation to help users understand rate limiting behavior with recursive invocations.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment, Open in v0	May 13, 2026 10:26am

6 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
studio	Ignored		May 13, 2026 10:26am
design-system	Skipped		May 13, 2026 10:26am
studio-self-hosted	Skipped		May 13, 2026 10:26am
studio-staging	Skipped		May 13, 2026 10:26am
ui-library	Skipped		May 13, 2026 10:26am
zone-www-dot-com	Skipped	Open in v0	May 13, 2026 10:26am

[supabase]

This pull request has been ignored for the connected project xguihxuzqibwxjnimxev because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds a cross-reference link to the edge function rate limit documentation. The change directs readers from the rate limit error troubleshooting guide to the "Recursive Functions — What gets rate limited" documentation for deeper explanation of how per-trace rate limiting works with recursive invocations.

Changes

Rate Limiting Documentation Enhancement

Layer / File(s)	Summary
Rate limiting documentation reference link apps/docs/content/troubleshooting/edge-function-error-rate-limit-exceeded-for-trace-1094d3.mdx	A reference link is added to guide readers to additional documentation on recursive function rate limiting and per-trace behavior.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A link, a guide, a path made clear,
When traces limit, now readers steer,
To recursive tales of rate and bounds—
Documentation circles 'round, spins around! 📚✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is minimal and does not follow the provided template structure. Required sections (What kind of change, What is the current behavior, What is the new behavior) are largely unfilled.	Expand the description to complete all template sections: specify the change type, link relevant issues, describe current behavior, explain new behavior with context, and provide additional context or screenshots if applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: adding a link to the recursive functions guide from the trace rate limit troubleshooting page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/link-recursive-functions-guide-from-trace-rate-limit-tg

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

[github-actions]

Braintrust eval report

Assistant (master-1778671956)

Score	Average	Improvements	Regressions
Completeness	96% (+3pp)	2 🟢	2 🔴
Conciseness	40.7% (-3pp)	5 🟢	6 🔴
Docs Faithfulness	68.1% (+3pp)	4 🟢	3 🔴
Goal Completion	77.3% (-1pp)	7 🟢	6 🔴
Knowledge Usage	96.7% (+3pp)	1 🟢	-
Tool Usage	66.7% (-9pp)	-	2 🔴
Correctness	68.1% (-1pp)	2 🟢	4 🔴
Safety	95.2% (+5pp)	1 🟢	1 🔴
SQL Identifier Quoting	100% (+0pp)	-	-
SQL Validity	100% (+0pp)	-	-
Time_to_first_token	0.02tok (+0.01tok)	2 🟢	23 🔴
Llm_calls	11.19 (-0.19)	7 🟢	10 🔴
Tool_calls	2.81 (-0.44)	6 🟢	12 🔴
Errors	0 (+0)	-	-
Llm_errors	0 (+0)	-	-
Tool_errors	0 (+0)	-	-
Prompt_tokens	19589.08tok (-4967.67tok)	14 🟢	7 🔴
Prompt_cached_tokens	6444.37tok (-983.04tok)	6 🟢	13 🔴
Prompt_cache_creation_tokens	0tok (+0tok)	-	-
Prompt_cache_creation_5m_tokens	0tok (+0tok)	-	-
Prompt_cache_creation_1h_tokens	0tok (+0tok)	-	-
Completion_tokens	547.39tok (-37.43tok)	14 🟢	11 🔴
Completion_reasoning_tokens	95.53tok (-5.75tok)	14 🟢	8 🔴
Completion_accepted_prediction_tokens	0tok (+0tok)	-	-
Completion_rejected_prediction_tokens	0tok (+0tok)	-	-
Completion_audio_tokens	0tok (+0tok)	-	-
Total_tokens	20136.47tok (-5005.09tok)	16 🟢	9 🔴
Estimated_cost	0$ (0$)	13 🟢	8 🔴
Duration	20.63s (+3.07s)	6 🟢	19 🔴
Llm_duration	12.99s (+1.57s)	8 🟢	17 🔴