any idea what's causing friday == saturday? : )
any idea what's causing friday == saturday? : )
any idea what's causing friday == saturday? : )
Interesting 😄 Well, what comes to mind is a potential hiccup with timezone. But not sure. Can you share the task url? Would like to look into this. How to share your Lindy task URL: 1. Click your Lindy agent → click “tasks” 2. Find the task you need help with 3. Click the specific task (you should see the full execution) 4. Copy that page URL from your browser 5. Paste the URL in your support request Note: The URL should include “conversationID” followed by a number 💡 Screenshots are also helpful!
The candidate asked to chat on Friday. The Lindy said Friday was March, 22nd, and that Friday falls on a Saturday.
That friday was actually March 21st, so that was the first error.
she does not recognize fridays or mondays as availalbe days for scheduling anymore. on Saturdays, she tells people she'll look for times on sunday, when that's not an available day. this has actually led to a complete breakdown in the use of the lindy, to the point where we've defaulted to just sending a calendly link 🤷♀️ my goal was to actually roll out copies of this lindy to multiple people on my team, but i'm blocked from doing so because of how critical the errors are.
looking into this. but short answer is yes — we have seen this Lindy work for all time zones. It’s a v common use case. Just need to figure out whats wrong here. 👀
Thanks! Other examples from the same Lindy: Friday's had openings, yet Lindy didn't interpret is as such. https://chat.lindy.ai/ivy-right-hand-talent-6716a11004753cd465224811/tasks?e=6716a11004753cd465224818&conversationId=67f6a969edafb47a685c73b4
Monday had openings, but Lindy proposed Tuesday instead, when she should propose the soonest times. Also it sent code stuff https://chat.lindy.ai/ivy-right-hand-talent-6716a11004753cd465224811/tasks?e=6716a11004753cd465224818&conversationId=67f6ad30ccca33cf949349c0
So I am still looking at the first task you shared earlier. The LLM definitely messed up the calendar days in the end— it looks like there is a small logic issue being the reason here: When it goes down the “there is a conflict” path → you put it back to the initial find available times which will try to find times. No matter if it actually found any —it will go into the conditions and choose the best one. This time it went ahead and replied with times (even though it didnt find any) First suggestion: Please change all calendar actions to use o1 (smartest LLM currently) → we use this on purpose on our meeting scheduler template too. Second: Solve for the edge case of it there is a conflict → find times → what if still no time is found?
lmk if that makes sense to you 🙂
I’ll talk to our engineer regarding the mentioned code in the reply. This is not supposed to happen at all. thx for sharing!
btw regarding the email with the code —can you confirm that the code was in fact visible inside the actual email? 🤔
Yes, it showed up in the email
quick update: the engineer has the same impression regarding the code + logic issue. The LLM went to look for available times → couldnt find any → was “forced” to write a reply due to the conditions → made up dates and tried to call the find available times action by writing it in the actual email bc there was no other option for the LLM to go for.
If there is no available time found, this prompt might also confuse the LLM
i see, i will update to "if there is no same-day availability offers six of the earliest available time slots for the next available weekday "
fyi this won’t solve for the underlying edge case issue I mentioned :)
Yea will so how edge it is after this prompt fix