Skip to content

Facebook/fix db - #669

Open
dhruvbhambani wants to merge 2 commits into
version-5-mainfrom
facebook/fix-DB
Open

Facebook/fix db#669
dhruvbhambani wants to merge 2 commits into
version-5-mainfrom
facebook/fix-DB

Conversation

@dhruvbhambani

Copy link
Copy Markdown
Collaborator

Summary

Brief description of what this PR does and why.

Fixes #(issue)

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation
  • Other: ___________

Testing

How has this been tested? What should reviewers focus on?

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

Dhruv Bhambani and others added 2 commits July 30, 2026 12:34
…cs for ad queries

Ad queries returned only a bare creative ID with no parent context, and any
timeframe the user asked for was silently dropped because entity endpoints
ignore the top-level date_preset.

Instruct the query model to expand nested objects (creative, campaign, adset)
and to attach metrics via nested insights with dot-notation parameters, which
the /ads edge supports. The deterministically extracted date selection is now
relayed to the prompt so the model uses the exact resolved preset or custom
range instead of inferring one.

Prompt-only: the request builder and Facebook API client are unchanged.
Co-authored-by: Cursor <cursoragent@cursor.com>
Expose Graph API rows directly through the declared data output so workflow variables and Chart Generator receive tabular data instead of the paging envelope.

Co-authored-by: Cursor <cursoragent@cursor.com>
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