Is Lindy AI Down?

If Prismix shows Lindy AI as "Operational" but you're having issues:

• Lindy workflow not triggering on new email (Gmail connector auth expired) — Lindy's Gmail trigger relies on an OAuth token that expires after a period of inactivity or when your Google account password changes. If your "on new email" Lindy stops firing, re-authenticate the Gmail connector from the Lindy integrations panel. You'll be prompted to re-grant inbox access.
• Meeting notes not generated (Zoom recording permission not granted) — Lindy's meeting notes feature requires access to Zoom cloud recordings. If notes are not appearing after a meeting, verify that the Lindy Zoom integration has been granted the recording:read OAuth scope and that cloud recording is enabled on your Zoom account (not just local recording).
• Workflow step timing out on slow third-party API — Lindy workflows have a per-step execution timeout. If a connected app (CRM, ticketing system, custom webhook) responds slowly, Lindy marks the step as failed and the workflow stops. Check the workflow run history in Lindy for timeout errors and either optimize the downstream API or split long-running steps into asynchronous sub-tasks.
• App integration token revoked after password change — changing the password on any connected account (Google, Slack, HubSpot, etc.) automatically invalidates existing OAuth tokens. After a password change, all Lindy integrations connected to that account will stop working until re-authenticated. Go to Lindy's integrations page and reconnect each affected service.
• Recurring task skipping runs (timezone mismatch in schedule) — Lindy schedules are stored in UTC internally. If you configured a recurring Lindy in a different timezone and then changed your system timezone or account locale, the schedule may shift. Verify your Lindy's schedule by opening the trigger settings and confirming the displayed time matches your intent in your local timezone.
• AI response not matching configured tone (system prompt override needed) — Lindy's default AI persona can produce responses that don't match the tone or style expected for your use case. To enforce a specific communication style (formal, concise, first-person), add a system prompt override in the Lindy's "Personality" or "Instructions" configuration block, specifying tone and format requirements explicitly.