Canonical page: https://tellenze.com/help/troubleshooting

Find and resolve common problems

Recover from missing access, stale edits, unavailable features, and delayed agent or integration work.

Start with the visible error

Read the message next to the action that failed. Record the page, work-item identifier, approximate time, expected result, and what actually happened. Keep a copy of unsaved text before refreshing or leaving an editor. When asking your workspace administrator for help, share these details and the relevant link; omit passwords, tokens, and unrelated private content.

The public Help center explains product behavior. It does not establish workspace membership or grant access to the feature described.

Resolve sign-in and invitation problems

An invitation must be accepted using the verified Emergent Accounts email it names. Check the address and expiry on the invitation page. If the link is unavailable, ask an administrator to inspect the invitation and resend it when appropriate. An administrator should check whether you already appear as a member before creating another invitation.

If a previously working account loses access, ask an administrator to check its Active or Suspended status. Restoring membership does not restore revoked MCP connections; those must be authorized again.

Find missing work or unavailable controls

Check which project, team, or saved view you are using, then review its filters and archive selection. Search results and links follow your current permissions. Ask someone with access to check the owning scope if the item still cannot be found.

A missing action may reflect your permissions, archived work, or a feature disabled for the installation. Workshop participation and review-edition readership have separate access rules. A link in a message does not grant those rights.

Recover from a save conflict

When the page says someone changed a record first, review the latest version before submitting again. Reconcile your intended changes with that version rather than repeatedly resending the old form. If a response was lost, reopen the record or its activity to check whether the action succeeded before repeating an operation that could create another item.

Restore agent and integration access

For an external agent, open MCP connections and inspect the current authorization and Machine profile. Follow the setup instructions displayed there to reconnect when access has expired. Verify your own access to the project and its saved local path mapping.

For Agent reactions, read the saved profile’s readiness blockers. Check the companion heartbeat, native provider sign-in, selected MCP connection, and workspace/provider availability. Use a retry control only when offered, and inspect existing outputs first.

For GitLab, distinguish cached data from current data and try the delivery panel’s Refresh action. An administrator can check token expiry, revalidate discovery, and confirm repository links. An empty Development section only means no matching recent activity was returned.

If several people see the same service failure, contact your workspace operator with the affected page, the time it happened, and any error reference shown. The operator can check the service’s health and monitoring.