fix: members_sorted schedule

[epipav]

No description provided.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

Conventional Commits FTW!

[cursor]

PR Summary

Low Risk
Single cron timing tweak with no query changes; the main risk is hourly ordering/freshness vs other staggered copy pipes if the new minute was chosen incorrectly.

Overview
Updates COPY_SCHEDULE on members_sorted_copy_pipe.pipe from 8 * * * * to 36 * * * *, so the replace copy into members_sorted runs later each hour instead of at :08.

No SQL or datasource logic changes—only when the filtered member snapshot (used downstream e.g. memberId IN (SELECT id FROM members_sorted) in activityRelations bucket enrich copies) is refreshed.

^{Reviewed by Cursor Bugbot for commit 79a057a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Copilot]

Pull request overview

Moves the hourly members_sorted Tinybird refresh from minute 8 to minute 36.

Changes:

• Updates the copy schedule to 36 * * * *.
• PR title is missing the required (CM-XXX) JIRA key.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.