fix: ignore results that have no activity data (CM-1112)

[themarolt]

Note

Medium Risk
Changes batch-processing behavior to treat missing activity payloads as successful/processed rather than failed, which can silently drop bad inputs but prevents whole-batch failures/crashes.

Overview
Prevents processActivities batches from failing when a payload has no activity data by skipping those items and marking their resultId as successfully processed, with a warning log.

Aligns prepareMemberData handling so missing activity no longer produces an UnrepeatableError; it now warns and returns success for that item, avoiding batch-wide errors from TypeError when accessing activity.username.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 72ac5c3. Configure here.}

[Copilot]

Pull request overview

This PR aims to prevent malformed activity results (where data.data is missing / not an activity object) from crashing a batch by treating them as “processed” and skipping further work.

Changes:

• Changes the !activity guard in prepareMemberData to log a warning and mark the result as success: true instead of failing with an UnrepeatableError.

---

💡 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 2 comments.

---

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