Does Pipedream's New Email in Shared Folder Event have a bug that prevents it from emitting events?

user-1 · November 22, 2025, 1:37am

This topic was automatically generated from Slack. You can find the original thread here.

Pipedream’s New Email in Shared Folder Event I believe has a bug (sample source/trigger: dc_6Ruqqvb)

Note in the logs the lastDate being updated (screenshot). This implies an event should be emitted.
However, note in events that no event was emitted at 10:21AM (when this trigger ran)
That said - looking at the code… it looks fine to me? I can’t really see an area where we are not emitting an item, unless something is erroring out in this.$emit but not showing up?

user-1 · November 22, 2025, 1:37am

Weirdly, when I redploy, the issue goes away for a bit, and then re-materializes later

user-1 · November 22, 2025, 1:37am

found it - id: item.conversationId

any email in a thread has the same conversationId.

This is why item.id is used in the receive mail api

user-1 · November 22, 2025, 1:37am

github.com/PipedreamHQ/pipedream

[BUG] Dedup key in Outlook Shared Email Received causing events to be dropped

opened 05:41PM - 28 Oct 25 UTC

closed 05:06PM - 06 Nov 25 UTC

alexpareto

bug triaged

**Describe the bug** ConversationID is used as the dedup ID for Shared Email Rec…eived, causing any follow up emails/emails in threads to not be received properly. Conversation ID identifies an email thread in outlook - not an individual email. See here: https://github.com/PipedreamHQ/pipedream/blob/36a8917969982afaa545f7577f28f3c0dde4466c/components/microsoft_outlook/sources/new-email-in-shared-folder/new-email-in-shared-folder.mjs#L70 [This is why item.id is used in the receive mail api](https://github.com/PipedreamHQ/pipedream/blob/36a8917969982afaa545f7577f28f3c0dde4466c/components/microsoft_outlook/sources/new-email/new-email.mjs#L47) **To Reproduce** Steps to reproduce the behavior: 1. Send email to shared inbox 2. Reply to that email 3. Note that the reply is not properly emitted **Expected behavior** New emails in the same email thread should be emitted **Screenshots** <img width="1596" height="668" alt="Image" src="https://github.com/user-attachments/assets/6f5706ae-f00c-41e9-92ac-d97684e863b6" /> <img width="333" height="320" alt="Image" src="https://github.com/user-attachments/assets/398210f6-3997-4763-8cc9-1d83947c6cb6" /> <img width="831" height="714" alt="Image" src="https://github.com/user-attachments/assets/e359079c-8dc3-4e55-b604-aab201bdbb49" />

user-1 · November 22, 2025, 1:37am

Got it , thank you so much for your effort

I’ve added your issue to the prioritized list. Our component dev will take a look at it very soon

user-1 · November 22, 2025, 1:37am

Posted thread to Discourse: Is there a bug in Pipedream's New Email in Shared Folder Event not emitting events despite updates in the logs?

user-1 · November 22, 2025, 1:37am

Hey - went to test this and I’m actually still seeing events being dropped here and not processing. Seems like there might be another issue.

See below on the timestamp update and no events were emitted.

Furthermore, I noticed only one event is emitted with the test suite, despite deploy asking for 25 (and this account having well over 25 emails). My sense is that there probably is still a bug with the dedup key

user-1 · November 22, 2025, 1:37am

Could you share steps to reproduce? How are you getting the email to the shared folder?

user-1 · November 22, 2025, 1:37am

Deploy trigger to a shared inbox trigger
a. Ensure the user.id is of a shared inbox that the logged in user has access to and not of the logged in user
Select “inbox” as the shared folder
Deploy source
Observe only 1 test event emitted
After deployed, send an email to the shared inbox
Observe no event emitted

user-1 · November 22, 2025, 1:37am

For Step 4 - while it’s a bug only 1 event is emitted, the fact that 1 event is emitted implies that the configuration of the trigger is correct I think and there’s something else going on

user-1 · November 22, 2025, 1:37am

In addition, when one redeploys with the exact same configuration, the email sent in step 5 is outputted as a test event - this implies that the inbox/email is showing up

user-1 · November 22, 2025, 1:37am

If helpful, here is a source I reproduced with, not sure if you all have more logs on your end:

Timestamp update is here, but then no event is emitted

user-1 · November 22, 2025, 1:37am

oh I think I know what it is

user-1 · November 22, 2025, 1:37am

github.com/PipedreamHQ/pipedream

components/microsoft_outlook/sources/new-email/new-email.mjs

master


      
                this.$emit(
                  {
                    email: item,
                  },
                  this.generateMeta(item),
                );
              }
            },
            generateMeta(item) {
              return {
                id: md5(item.id), // id > 64 characters, so dedupe on hash of id
                summary: `New email (ID:${item.id})`,
                ts: Date.parse(item.createdDateTime),
              };
            },
          },
          async run(event) {
            const folders = this.folderIds?.length
              ? this.folderIds.map((id) => `/me/mailFolders/${id}/messages`)
              : [
                "/me/messages",

In new email, the ID is hashed b/c >64 characters. Maybe pipedream cache doesn’t work over 64 characters? and/or the microsoft one is the same for first for 64 characters

user-1 · November 22, 2025, 1:37am

https://github.com/PipedreamHQ/pipedream/blob/master/components/microsoft_outlook/[…]urces/new-email-in-shared-folder/new-email-in-shared-folder.mjs

shared folder is just raw ID, no hash

user-1 · November 22, 2025, 1:37am

[18884] Update new-email-in-shared-folder.mjs by alexpareto · Pull Request #19077 · PipedreamHQ/pipedream · GitHub think this should fix it

user-1 · November 22, 2025, 1:37am

or something similar

user-1 · November 22, 2025, 1:37am

To make sure the fix works, I’ll need to reproduce the issue first. Right now I have not yet be able to reproduce it

user-1 · November 22, 2025, 1:37am

Interesting, you’re getting new events in a shared folder?

user-1 · November 22, 2025, 1:37am

I wonder if it’s related to my account being a business account vs a personal account? Not sure.

I checked two subsequent emails and the IDs are very similar - the only difference is this one character. So if there is some kind of 64 char limit, it would break things in this particular account.

But perhaps different microsoft accounts have different ID strategies? how different are the IDs you are using?