Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] Google Drive - New Files (Instant): Folders prop did not load #8446

Closed
vunguyenhung opened this issue Oct 12, 2023 · 3 comments
Closed

[BUG] Google Drive - New Files (Instant): Folders prop did not load #8446

vunguyenhung opened this issue Oct 12, 2023 · 3 comments
Labels
bug Something isn't working triaged For maintainers: This issue has been triaged by a Pipedream employee
Projects
Component (Source and Action) Backlog

Comments

@vunguyenhung
Copy link
Collaborator

Describe the bug
When attempt to create the Google Drive - New Files (Instant) source and select the Folders prop, I didn't see the Folders prop load and there's no reaction when clicking into the Folders prop
image

Even though I have many folders in my Drive
image

Expected behavior

  • The Folders prop should load all folders I have
  • The source should be created successfully

Additional context
Reported by a user here: https://pipedream-users.slack.com/archives/CMZG4EBJ9/p1697107482191509
@vunguyenhung vunguyenhung added the bug Something isn't working label Oct 12, 2023
@vunguyenhung vunguyenhung added this to To Do in Component (Source and Action) Backlog via automation Oct 12, 2023
@dylburger dylburger added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Oct 12, 2023
@mroy-seedbox
Copy link
Contributor

Would love to see this fixed also!

For now, we worked around it by using shared folders instead of My Drive, but that doesn't cover every use case.

@dylburger dylburger moved this from To Do to Prioritized in Component (Source and Action) Backlog Oct 13, 2023
@dylburger
Copy link
Contributor

This should be fixed. Please reload https://pipedream.com/ and try to configure the trigger again. Let us know if you see any other related issues.

Component (Source and Action) Backlog automation moved this from Prioritized to Done Oct 13, 2023
@jahooli14
Copy link

This is great, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working triaged For maintainers: This issue has been triaged by a Pipedream employee
Projects
Component (Source and Action) Backlog
  
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dylburger @vunguyenhung @mroy-seedbox @jahooli14