Microsoft Teams - Stop triggers from unnecessarily emitting every event every run

[JHawk0224]

WHY

On line 65, the value saved with _setLastCreated is already parsed as a unix timestamp. Thus when getting the value, there's no reason to call Date.parse again. It's already in the correct format.

In fact, this actually breaks it and returns NaN. This then causes every event to be emitted unnecessarily. I believe the only reason this still actually works is because of the dedupe: "unique", but that's just a guess - I'm not too sure.

---

Important Note

There is a larger issue at play here (new issue) where every resource is paginated through every time a trigger is run. For the New Chat Message trigger, this causes storage/memory issues for significantly sized chats:

It makes sense to paginate through every resource for some of the triggers which have no intrinsic ordering, like get channels, but for triggers that have an order by created date, like get channel/chat messages, this makes no sense. Only the events since the last checked time need to be fetched from the api, so there's no point in paginating through every possible resource.

Summary by CodeRabbit

• Bug Fixes
  • Improved initial sync for Microsoft Teams sources to reduce missed or duplicate items.
  • More reliable detection of newly created messages and events across runs.
  • Consistent pagination and filtering on first run for smoother onboarding.
  • Stabilized time-based comparisons to minimize edge cases during update checks.
  • Overall increases in sync reliability and data freshness for Microsoft Teams integrations.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs-redirect-do-not-edit	Ignored			Oct 3, 2025 4:22pm

[coderabbitai]

Walkthrough

Adjusted handling of lastCreated in components/microsoft_teams/sources/common/base.mjs: initial assignment now uses _getLastCreated() directly instead of Date.parse, while subsequent updates still use Date.parse(createdDateTime). getResources continues to receive lastCreated; persistence stores lastCreated after loop.

Changes

Cohort / File(s)	Summary of edits
Microsoft Teams source base components/microsoft_teams/sources/common/base.mjs	Changed run() to assign lastCreated directly from _getLastCreated() (no initial Date.parse). Inside loop, lastCreated is set to Date.parse(createdDateTime). getResources is called with potentially non-numeric lastCreated on first call; final _setLastCreated(lastCreated) persists the post-loop value. No exported API changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I nibble timestamps, crunchy and bright,
First a string, then numbers take flight—
Hop, hop, through messages new,
I stash the latest in a burrowed queue.
Code carrots sorted, neatly arranged,
One tiny hop, the flow’s unchanged. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly identifies the Microsoft Teams integration and clearly summarizes the main change to prevent triggers from emitting every event on each run, making it specific and relevant to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Description Check	✅ Passed	The pull request description includes the required “## WHY” section with a clear explanation of why the change is needed, describes the issue with parsing the stored timestamp, and outlines the impact on event emission; it also provides additional context in an “Important Note,” all in line with the repository’s template.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible
• Create subscription webhooks sources (vs polling sources) whenever possible
• Always emit a summary with events
• Use a built-in deduping strategy wherever possible
• When building webhook sources, follow these best practices
• When building polling sources, follow these best practices