Skip to content

[BUG] Microsoft Teams - Triggers paginate through every resource on every run #18634

@JHawk0224

Description

@JHawk0224

Describe the bug

For Microsoft Teams triggers (sources), 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:

Screenshot 2025-10-03 at 1 14 03 PM

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.

To Reproduce
Steps to reproduce the behavior:

  1. Have a very large Microsoft Teams chat
  2. Create a Microsoft Teams New Chat Message trigger for that chat
  3. Send a new message
  4. See error

Expected behavior
For triggers based on resources with some ordering, only the resources since the last fetch need to be fetched. There's no reason to paginate through every single resource without filtering at all.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingtriagedFor maintainers: This issue has been triaged by a Pipedream employee

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions