Ross

I encountered the same problem with using the google drive file change trigger (long wait time, or in some cases no notification at all). It was not consistent enough that I could debug it, so I went down another path.

I have run into this too, where the interface is not showing the agent, but the agent is there. Solution, log out of Lindy, close the tab, log in again, the agent will be visible. Not a great workaround, but it does solve the problem. But, one time that did not work either. I had to delete the agent to get it to stop consuming credits.

My Connection to a Neon database using Postgres is rock solid. It takes a bit to 'warm up', but that keeps the cost of the Neon DB < $5 per month for my use case.

Hi, Sadly, Pro doesn't show up for me. Here's a screen shot. This is using an 'Agent Step'. Are you sure that pro (not auto, mini, nano, or chat) is in general availability in Lindy.ai Kourtney G.

From what I have observed, yes to the limits of how long the login session lasts for a normal user. I have not tested LinkedIn and Facebook specifically. Google did work for me. What messes things up is reauthentication with a frequency + 2FA.

I agree, and loops are fraught with danger 'eating credits'

yes, any parallelization using Lindy constructs would require parallel. My answer was if you wanted agents in different lindy accounts to work. I don't think agent messages cross the 'account' barrier. Or, you could do it with code. Call computer use, create webhook messages there, and then the agent will suddenly get say 10 triggers for 10 messages, thereby creating 10 tasks

I would go with webhooks for invoking agent to agent calls.

HI, just a reminder, only when you use the 'test' button, do you get up to 500 'test' credits. So best to test with that button, and not by deploying for real.

yay!!! thanks Kourtney G.