URGENT HELP NEEDED! Query Service on a Snapshot dataset for a specific audience | Community
Skip to main content
Level 4
May 28, 2026
Solved

URGENT HELP NEEDED! Query Service on a Snapshot dataset for a specific audience

  • May 28, 2026
  • 2 replies
  • 48 views

All, 

 

Has something changed with the Snaphot dataset, specifically the segmentMembership. The following Query used to work for me, but no longer does: 

SELECT
  channel,
  COUNT(*) AS eventCount
FROM
  (
    SELECT
      EXPLODE (_cocacola.communicationChannel.channel) AS channel
    FROM
      profile_snapshot_export_c495eb9a_5571_46e2_9ccd_310042dddc72 SNAPSHOT AS OF 1588
    WHERE
      segmentMembership['ups']['a0bd3286-e38c-4c44-b037-d2f9d8a2cf81']['status'] IN ('existing', 'realized', 'exited')
  ) AS exploded
GROUP BY
  channel

 

I pulled the most current ID and then searched for the segmentID of the audience I need to take a count on, but I get 0 returns now. Does anyone know what’s changed? 

    Best answer by montezh2001

    FYI… I fixed this. I was missing a JOIN on another schema where the channel attribute lives. 

    2 replies

    Pulkit_Jain_
    Adobe Employee
    Adobe Employee
    June 1, 2026

    @montezh2001 It’s very likely not your query but your snapshot dataset no longer contains segmentMembership, or you are querying an outdated snapshot ID.

    Several recent internal issues have been reported that UPS snapshot exports can temporarily drop or stop writing segmentMembership, causing queries that previously worked to suddenly return zero rows.

    You can run snapshot_meta() to find the latest snapshot and query the newest snapshot without “AS OF 1588”, to check if segmentMembership exists in that snapshot. 
    If it’s missing there too -> it's a known snapshot/export issue, not a SQL problem.

    Level 4
    June 1, 2026

    Thank you. I’m sure this is the issue as I ran the Meta query and use the most current Snapshot ID. I will need to reach out to Adobe Support. Appreciate the response. 

    montezh2001AuthorAccepted solution
    Level 4
    June 3, 2026

    FYI… I fixed this. I was missing a JOIN on another schema where the channel attribute lives.