Skip to content

meta-ads-pp-cli 2026.6.2: cannot sync account-scoped resources; inventory hint references non-existent --path-context flag; all local-store analytics empty #1434

Description

@cryptoury

Summary

In meta-ads-pp-cli 2026.6.2 the local store never receives account-scoped resources (campaigns, adsets, ads, insights). sync and workflow archive only sync the me resource, and there is no working way to scope a sync to an ad account. As a result every local-store analytics command (fatigue, bottleneck, inventory, decay, learning, stale) returns empty.

Environment

  • meta-ads-pp-cli 2026.6.2 (installed via npx -y @mvanhorn/printing-press-library install meta-ads)
  • macOS (darwin/arm64), Go 1.26.3
  • Auth: Business Manager system-user token with ads_read; live reads work (me returns the ad account, campaigns <adAccountId> returns campaign ids)

Repro

  1. meta-ads-pp-cli sync -> only me syncs: {"event":"sync_summary","total_records":1,"resources":1,...}

  2. meta-ads-pp-cli workflow archive -> same: "Archived 1 items across 1 resources"

  3. meta-ads-pp-cli inventory act_<id> -> "total_ads": 0 with this hint:

    run 'meta-ads-pp-cli sync --path-context adAccountId=act_ --resources ads' first

  4. But that flag does not exist in this build:

    meta-ads-pp-cli sync --path-context adAccountId=act_<id> --resources ads
    Error: unknown flag: --path-context
    
  5. Attempts with the documented generic flags also fail, with no error detail:

    meta-ads-pp-cli sync --resources ads,campaigns,adsets --global-param adAccountId=act_<id>
    {"event":"sync_summary","total_records":0,"resources":3,"success":0,"warned":0,"errored":3,"duration_ms":0}
    Error: 3 resource(s) failed to sync
    

    duration_ms: 0 suggests the resources fail before any request is made (missing path context), but no reason is emitted.

Expected

Either --path-context exists as the inventory hint says, or the sync spec resolves ad account ids from the already-synced me resource and cascades into campaigns/adsets/ads/insights. Also, per-resource failures would be much easier to debug if the summary carried a reason field.

Impact

The compound analytics commands are the headline features of this CLI and none of them can run without the local store. Live one-shot reads are unaffected.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions