Troubleshooting

Start with the symptom below. If you have unsynced work, preserve it before signing out, clearing site data, or reinstalling.

Account issues

1. Confirm you are using the LFG account that owns or was invited to the project.
2. If verification is required, use the newest verification email and check spam or junk.
3. For a forgotten password, use the recovery option on sign-in. Google sign-in passwords are managed through Google.
4. If an invitation is bound to an email, sign in with that matching account.

See sign-in and account. Never send passwords or access tokens to support.

Missing projects or items

1. Check the selected project and signed-in account.
2. Clear search and filters, then check Active, Complete, and Trash.
3. Search the item key or title within the expected project. A nonblank app search covers all three views.
4. If the project is archived, turn on Show archived projects in the account menu.
5. Reconnect if offline. This device may not have the item’s page or full details cached.
6. For shared work, ask the owner to check your membership and Pro access. Do not create duplicate work until you have ruled out access or view restrictions.

Search and view behavior · restore an item

Item editing issues

• Saved offline: the change is local. Reconnect, return to the app, and allow sync to finish. Confirm Saved before checking another device.
• Validation error: read the message and correct the affected input. Closing the item does not cancel its edits.
• Newer conflicting edit: inspect the current item before retrying. Preserve your text separately if needed; do not blindly overwrite someone else’s change.
• Cannot edit: check whether you are a Viewer, the item is in Trash, the project is archived, or the field needs Pro.
• Stale details: reopen the item while online to retrieve current information. If an operation still fails, capture its error and item key.

Do not clear browser storage or reinstall as a first attempt to fix queued changes. Follow offline recovery.

A repeating item did not create its successor

Confirm Repeat is set and the item has a due date. Then check what action actually happened: moving to a Complete status or a configured check-to-Trash action can advance recurrence; explicitly choosing Move to trash does not. Reconnect if the action was queued offline.

See due dates and repeat.

Reminders not arriving

1. Confirm Pro access and your account timezone.
2. In Settings → Notifications, enable Notify me about due items.
3. On Android, enable Notifications on this device and check Android notification settings for system permission.
4. In Project settings → Notifications, choose Follow account setting for your reminders.
5. Confirm the item is active, not trashed, due in the relevant reminder window, and created by or assigned to you. An archived project is not eligible.

Daily recurrence skips the day-before reminder; overdue reminders are sent on the first overdue morning, not indefinitely. Browser builds do not provide Android device delivery. See reminder timing.

Permissions and unavailable controls

A disabled or missing control can reflect your role, plan, project state, or connection. Owners/Admins configure projects; Contributors edit items; Viewers read. Personal projects have no sharing controls. Shared projects require Pro for the owner and every participant.

Check roles and plan limits before treating this as an app failure.

MCP issues

1. Confirm Pro is active for the token owner.
2. Use https://mcp.lfglist.com/mcp, remote Streamable HTTP, and Authorization: Bearer <token>.
3. Check Settings → Integrations → Access tokens to confirm the token is active. If revoked or lost, create a replacement and update the client’s trusted configuration.
4. Reconnect the MCP client and test list_projects.
5. If a project is missing, verify membership and account. If an action is unavailable, check the tools reference.

An expired invitation, a role restriction, and an invalid token are different problems; replacing the token will not fix all three. See connection setup.

Still blocked

Contact support with the expected behavior, actual behavior, exact error, project/item key, device, app version, and whether you were offline. Keep passwords and tokens out of screenshots and messages.