Marvin A. I noticed several issues when sharing a Lindy in my community today. The file was shared with an onboarding sequence. Issues:
The contents Prompt AI fields in the Google Docs action weren't preserved (the prompts were missing).
Additionally, the Google Drive Knowledge Base did not sync the contents, so the agent Q&A didn't work. I had to manually remove the knowledge base folder from the files list and add the folder back again to get it to sync properly.
Marvin A. Any idea when #1 will be fixed? This is impacting client deployment feasibility. Regarding #2, it seems that the Drive Folder must contain at least 1 asset in order for the syncing to start working. E.g. you can't point to an empty folder and then add to it, without causing issues.
Marvin A. the Lindy sharing is super unreliable. Many of the parameters and fields do not maintain settings/inputs. I attempted to deploy several agents today (client deliverables) and had to reschedule due to inconsistencies in the shared vs developed workflows. I'd love to talk more specifically about these issues, as this is a roadblock for future client implementations.
Anybody know if this syncing issue has been fixed yet? I too am running into this problem and having to get the client to manually sync each time
Hey Charlotte! Unfortunately this is part of a bigger issue the team has been tackling. Will keep you posted!
When you say manually sync each time , do you mean: you shared a template → the install → some fields are missing configuration?
I mean, I asked it to refer to a googlesheet for knowledge, and it doesn't take the latest updates to then conduct the task, it takes a verison from 22 hours ago or several days ago. When I click on last synced it'll say the time elapsed- even though autosync is turned on
Marvin A. Ethan K. Any updates on this issue:
The contents Prompt AI fields in the Google Docs action weren't preserved (the prompts were missing). Posted on June 13th (3 months ago).
This is preventing my clients and community members from successfully deploying agents I build, without my direct involvement in the deployment.
