Lattice Not Working? Common Errors & Fixes

Lattice 1:1s stop syncing when the recurring calendar event is deleted or recreated, the next meeting is past the sync window, or calendar authorization breaks. The creator of the 1:1 can fix it from the 1:1's Settings > Calendar event sync, then reconnect the calendar.

This error appears when your Microsoft Entra ID tenant blocks users from consenting to third-party apps. A Microsoft admin has to connect Outlook in Lattice once and accept the permissions; then everyone else can connect.

The generic 'Something went wrong' message in Lattice is usually a stale cache or an outdated browser; a hard refresh and a browser update fix most cases. If a whole page (like compensation recommendations) errors for everyone, check status.lattice.com for an incident.

If Lattice won't submit your performance review, a required question is almost always unanswered (marked with a red asterisk, sometimes needing both a rating and a comment). Otherwise refresh, log out and back in, or switch browsers, after copying your text somewhere safe.

Lattice stops emailing you if you ever unsubscribed or marked a Lattice email as spam, if your notification settings are off, or if your address hard-bounced. Customer Care can re-subscribe a suppressed address; if nobody in the company gets emails, IT needs to allowlist Lattice's sender.

Most Lattice login failures come from using the wrong login URL ([account].latticehq.com/login), an email that doesn't match your Lattice account, or an SSO setup where you aren't assigned to Lattice in your identity provider. Super admins can bypass SSO with a password.

Lattice's Slack app fails most often because a user's Slack email doesn't match their Lattice email, the bot isn't in a private channel, or the channel is admin-only. Long posts over Slack's 3,000-character limit also fail; for Slackbot/MCP features, disconnect and reconnect.

When employees or changes don't come over from BambooHR, ADP or another HRIS, Lattice's Import Log usually shows a 'Missing field' error. Fill the field in the HRIS (e.g. BambooHR Pay Type, ADP Work Email), then run a manual sync from Admin > Settings > Platform > Integrations.

Lattice pulls Jira progress into goals once an hour from a JQL query on Jira Cloud only. Progress looks stuck when the query excludes subtasks, the JQL is invalid, the goal was disconnected, or a Lattice incident hit the integration.

A Lattice review cycle snapshots employee field data (department, manager, location) at launch, so later changes show in the directory but not in the cycle's filters, calibration groups or analytics. Only Customer Care can refresh analytics for an active cycle.

Lattice ended Payroll on March 31, 2026 and HRIS on July 31, 2026; historical HRIS data is not available after shutdown. Former HRIS customers need another HRIS and connect it to Lattice's performance products through the standard HRIS integration.