Lindy AI Agent Not Responding to Events or Messages: Fix Guide
You set up a Lindy agent as an internal meeting assistant. It's supposed to check your Google Calendar every morning at 8 AM, pull the day's meetings, draft a preparation brief for each one using context from your Notion workspace, and send you a summary email. It worked for the first week. Now it's been three days with no morning email. You open Lindy and look at the agent's run history. Either it's completely empty for the last three days, or the runs show as completed but the email was never sent. This is one of the more confusing failure modes in Lindy because the UI doesn't always make it obvious where things went wrong.
What this error actually means
Lindy agents operate on a combination of scheduled triggers (cron-style, like "every morning at 8 AM") and event triggers (like "when a new email arrives" or "when a Slack message mentions me"). When an agent stops responding, it means either the trigger isn't firing, the trigger fires but the agent's action steps are failing silently, or the agent is running but a downstream tool connection (Gmail, Notion, Calendar) is broken and the error isn't surfaced visibly.
Lindy's architecture runs agents server-side on Lindy's infrastructure. Unlike browser-based tools like Bardeen, Lindy doesn't depend on your computer being on. But it does depend on your connected accounts having valid authorization tokens and the agent being in an "Active" state.
Quick fix (when you need it working in 60 seconds)
- Open Lindy and click on the non-responding agent. Look for a status indicator near the agent's name. Confirm it says "Active" or "On." If it shows "Paused" or any warning icon, click it and activate the agent.
- Click "Run now" (or "Test run") to trigger the agent manually. Watch the run log that appears in real time.
- If the manual run completes but the email still doesn't arrive, check whether Gmail shows the email in "Sent" but Gmail's own spam filter diverted it.
- If the manual run fails with an error on a specific step, note the step name and the error message. Usually it will say something like "Google Calendar: authorization required" or "Notion: page not found."
- Go to Lindy's Integrations panel and reconnect the failing integration. Then re-run the agent manually to confirm it works.
Why this happens
The most common cause of a Lindy agent going quiet is an expired OAuth token for a connected integration. Google's OAuth tokens for Google Calendar and Gmail have a refresh window, but if Lindy's connection wasn't used for a long time, or if you changed your Google account password, the refresh token can be invalidated. Lindy's scheduler will attempt to run the agent, hit an auth error on the Calendar or Gmail step, and either record a failed run or drop it depending on how the specific integration handles the error.
Scheduled trigger issues are the second most common cause. Lindy's scheduling system uses UTC internally. If you set a trigger for "8 AM," it defaults to 8 AM UTC unless you explicitly set your timezone in Lindy's account settings. Many users who set up Lindy without setting their timezone find that their agent runs at an unexpected local time, or appears not to run at all because the run happens at 1 AM local time while they're asleep and the email arrives overnight rather than in the morning.
Notion integration failures are particularly common in Lindy setups because Notion's API access is scoped to specific pages and databases. If someone reorganized your Notion workspace, moved the page your Lindy agent was reading, or changed the sharing permissions, the agent's Notion steps will fail with a "page not found" or "unauthorized" error. Lindy may or may not surface this error prominently depending on how the step handles Notion's 404 response.
A less common but real cause is Lindy's own platform behavior around agents that have repeated errors. If an agent fails on several consecutive scheduled runs, Lindy may automatically pause it to prevent repeated failures from consuming compute resources. When this happens, the agent's status indicator changes, but you only notice if you check the agent dashboard. There's no email notification by default.
Permanent fix
- Set your timezone explicitly. Go to Lindy Account Settings > Time and Language, and set your timezone to your actual local timezone. Then recheck your scheduled trigger in the agent's trigger configuration and confirm the displayed time matches your expectation in local time.
- Reconnect all integrations. Go to Integrations in Lindy's left sidebar, click each connected service (Google Calendar, Gmail, Notion), and click "Reconnect." Even if they appear connected, a reconnect refreshes the OAuth token and resolves most silent auth failures.
- After reconnecting, re-authorize Lindy's access to the specific Notion pages your agent reads. In Notion, go to the settings for each relevant page and confirm that the Lindy integration (listed under "Connections") has access. Notion's granular permission model means new pages are not automatically accessible to existing integrations.
- Review your agent's run log for the last 7 days. Click the agent name, then click "History" or "Runs." Look for any run that shows a non-green status. Click each failed run to see which step caused the issue.
- Add a notification step to your agent as the first action step (before Calendar, Notion, or Gmail). Set it to send you a quick Slack DM or a one-line email: "Morning brief agent started at [timestamp]." This gives you a reliable heartbeat. If the heartbeat message stops arriving, you know the trigger itself is broken, not the action steps.
- Check Lindy's spam detection settings. In some cases, Lindy's outbound emails through Gmail are classified as automated messages and filtered. In your Gmail settings, create a filter that marks any email from
[email protected]or your own address (if Lindy sends on your behalf) as not-spam and stars it. - If you're using Lindy's built-in email sending rather than Gmail, check your Lindy notification preferences. Some account configurations route agent emails to Lindy's in-app inbox rather than your actual email address. Go to Settings > Notifications and confirm "Agent run summaries" is set to send to your email, not just in-app.
- For critical daily agents, set up a fallback monitoring alert. Use a simple Zapier or Make scenario that checks whether a specific Google Sheet row (that your Lindy agent should update daily) was modified in the last 24 hours. If not, the monitoring scenario sends you an alert. This gives you an independent check on Lindy's reliability.
Prevention
Set a calendar reminder to check your Lindy agents once a week for the first month after setup. During that period you're still learning the failure modes specific to your connected apps and timezone configuration. After a month of reliable operation, monthly checks are sufficient.
Keep your connected accounts stable. If you change your Google password, update your Notion workspace structure, or move to a new email provider, expect Lindy integration connections to need refreshing. Make it a habit to open Lindy's Integration panel and verify connections after any account-level changes.
Use Lindy's "Test run" feature after making any changes to an agent's configuration. Don't assume that a change that looks correct will work correctly. A test run with real data takes 30 seconds and tells you definitively whether the agent is healthy before you rely on it for your morning workflow.
When the fix doesn't work
If you've reconnected integrations, fixed the timezone, confirmed the agent is active, and the scheduled trigger still doesn't fire, open Lindy's support chat (the question mark icon in the bottom right of the app). Lindy's support team can check whether the scheduler is correctly queued for your agent and whether there's a platform-side issue affecting your account.
If the manual "Run now" works but the scheduled trigger doesn't, this points specifically to Lindy's cron scheduler rather than your integration configuration. This is a platform bug, not a user configuration issue. Report it to support with your agent name, your timezone setting, and the times of the most recent missed runs.
For use cases that require near-100% reliability (daily briefings for a sales team, customer-facing response automations), consider pairing Lindy with an external trigger. Set up a Zapier schedule trigger at 8 AM local time that sends a webhook to Lindy's API to start the agent run. This removes Lindy's internal scheduler as a dependency and uses a more battle-tested scheduling layer.