This topic was automatically generated from Slack. You can find the original thread here.
Hello! Pipedream recently made a bug fix for MongoDB to allow a timestamp to be used based on an issue I had previously, so all previous mongo db documents are not fetched by default. I’ve tried restarting my workflow but the MongoDB doesn’t appear to be triggering at all. Has a change been made to how collections are defined? Previously, I would manually enter the collection name rather than from a dropdown list (due to the mongodb auth permissions) but now it doesn’t look like you can manually enter a collection name.
would manually enter the collection name rather than from a dropdown list (due to the mongodb auth permissions) but now it doesn’t look like you can manually enter a collection name
Hi , would you mind sharing the screenshot of your issue?
Hi I don’t see an error but I cannot see any events coming through. Before the bugfix it was working fine, I then paused the workflow, and once the bug was fixed, I have just resumed the workflow and not seeing any events.
One thing I have noticed is that the collection form field used to have an option to manually enter the collection name rather than from a dropdown list. The MongoDB we use doesn’t give us permission to list collections, so we have to manually enter it. I’m wondering if this has changed since the bugfix?
Hmm, I think this might be because of the recent change with the Pipedream platform that you can not input manually on source when the async options don’t work.
I’ll create a ticket on the Pipedream side to fix this.
Aside from that, on the paused workflow, would you mind accessing your Pipedream Source Page, select your source and sharing your source logs?
