Lindy Community Icon

Home
Events

00 Announcements
01 General
02 Support
03 Bugs
04 Requests and Feedback
05 Share Your Lindy
06 Intros

Community Guidelines

Troubleshooting Guide

Powered by Tightknit

Troubleshooting Slack Bot: Fixing Unexpected Error Issues | Lindy Community

Troubleshooting Slack Bot: Fixing Unexpected Error Issues

·Apr 17, 2025 02:54 PM·

Hey, Im trying out a simple slack bot that answers questions by reading a knowledge base but all I ever get is 'An unexpected error occurred'.

13 comments

· Sorted by Oldest

Marvin A.
·
·
Hey can you please share the task url? happy to look into this
Marvin A.
·
·
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!
Count F.
·
·
this is just a test. Maybe im using it wrong. I just added some test text and then Im asking questions about it. https://chat.lindy.ai/home/?templateId=68015d59218fa33f85cb3dd4
Marvin A.
·
·
That’s the template URL — can you share the task url where you saw the error? (If no task is available → send the Lindy URL from the browser)
Marvin A.
·
·
+ Screenshot if possible
Count F.
·
·
im not sure how to share the task url. WHen im on the task and click share, it seems to convert to a template url
Count F.
·
·
here is my browser url: https://chat.lindy.ai/support-slackbot-6801093e4b58850a7f83fadb/tasks?task=68011520e725339e8e615cee
Marvin A.
·
·
that’s the one! 🙂
Marvin A.
·
·
Yeah I am 95% sure this was related to a bug in our KB that’s been fixed on Monday! Can you give it another try? Count F.
Count F.
·
·
nope, still the same error
Marvin A.
·
·
Did you resync the KB? → remove all KB entries and add them back pls 🙂
Count F.
·
·
I deleted and readded the knowledge base in the flow but I still get the same error
👀1
Marvin A.
·
·
will have the team look into this and report back!