Skip to content

fix(prerender): skip creating suggestions for deployed-at-edge URLs when domain is fully deployed#2310

Draft
anuj-adobe wants to merge 1 commit intomainfrom
fix/prerender-skip-deployed-suggestions
Draft

fix(prerender): skip creating suggestions for deployed-at-edge URLs when domain is fully deployed#2310
anuj-adobe wants to merge 1 commit intomainfrom
fix/prerender-skip-deployed-suggestions

Conversation

@anuj-adobe
Copy link
Copy Markdown
Contributor

Summary

When the domain-wide suggestion has edgeDeployed set (isAllDomainDeployedAtEdge=true), individual suggestions for URLs already deployed at edge were being created as NEW and immediately moved to SKIPPED — a wasteful two-step cycle.

  • After convertToOpportunity, check isAllDomainDeployedAtEdge and exclude isDeployedAtEdge=true URLs from syncSuggestions newData — they are never created in the first place
  • Existing SKIPPED suggestions for deployed URLs are safe from OUTDATED because scrapedUrlsSet already excludes isDeployedAtEdge=true URLs from OUTDATED detection
  • Non-deployed URLs and the domain-wide aggregate suggestion are unaffected

Cases verified

Case Behavior
Domain-wide deployed (edgeDeployed on domain-wide suggestion) isDeployedAtEdge=true URLs filtered from newData — no NEW suggestion created; existing SKIPPED stays SKIPPED ✓
LLMO side-effect deployed (no domain-wide edgeDeployed) isAllDomainDeployedAtEdge=false — filter not applied, NEW suggestion created as before ✓
RCV-deployed individual suggestion (edgeDeployed on URL suggestion) Not in scrapedUrlsSet, not in newData — preserved untouched ✓

Test plan

  • Verify no new NEW suggestions are created for deployed-at-edge URLs when domain is fully deployed
  • Verify existing SKIPPED suggestions remain SKIPPED across audit runs
  • Verify non-deployed URLs still get suggestions created normally

🤖 Generated with Claude Code

…hen domain is fully deployed

When the domain-wide suggestion has edgeDeployed set (isAllDomainDeployedAtEdge=true),
individual suggestions for URLs already deployed at edge are excluded from syncSuggestions
newData instead of being created as NEW and immediately moved to SKIPPED.

Existing SKIPPED suggestions for deployed URLs are safe from OUTDATED because
scrapedUrlsSet already excludes isDeployedAtEdge=true URLs from OUTDATED detection.
Non-deployed URLs and the domain-wide aggregate suggestion are unaffected.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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.

1 participant