Why is MongoDB Trigger Continuously Showing "Waiting for Events" Despite Successful Connections and Proper Firewall Settings?

Bugs
21

sure

22

Ok seems like the code isn’t picking up any documents at all, I’ll create an issue for our component team to look deeper at it

23

I was hoping the quick small fix would do it but unfortunately it didn’t

24

Here’s the issue you can track: [BUG] MongoDB trigger not emitting events · Issue #16805 · PipedreamHQ/pipedream · GitHub, I added to the prioritized list

25

I will be waiting

26

Hi no updates yet

27

I have tried again after adding new document, still shows me “waiting for the event”

28

any updates?

29

we are getting blocker cuz of pipedream, can you help out

30

Just to confirm, did you create a new trigger when testing again?

31

yes tried multiple times

32

I’ll take a look at it again when possible (got a lot going on)

33

please kindly reveiw this as soon as you can, as its huge blocker for us, rest of the website is built and ready to launch

34

I published a new version with a ISO date option, which is the case for your MongoDB documents

35

Can you try again?

36

tested out by adding new trigger again, and adding new doc as well. still showing “waiting for the event”

37

Did you click on run now after you added the new doc?

38

yes, i did that

39

nothing working

40

I clicked run now and then added the doc