> ## Documentation Index
> Fetch the complete documentation index at: https://learn.biq.li/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot messaging

> Resolve sign-in, send, incoming-update, microphone, notification and restriction problems.

Identify whether the problem is authentication, sending, receiving live updates, recording or email delivery. Keep the exact error and time, but never share login codes or account credentials.

## Cannot sign in from a Biolink

Use the current email code for the address entered in that flow. Request another code when expired and respect resend or attempt limits. Follow any two-factor or organization sign-in step.

A social login can identify a different Biqli account from an email login. Compare account identity before concluding that a security challenge was skipped. Suspended or deletion-pending accounts may be unavailable.

On custom domains, secure authentication can open the main app and return to the Biolink. Allow that return to finish before retrying. See [Biolink messaging](https://learn.biq.li/help/messaging/biolink.md).

## Composer is disabled

Check the displayed reason. A block, account unavailability or moderation restriction can prevent sending. For temporary restrictions, inspect the effective expiry; another active restriction can remain after one is lifted.

A restriction cannot be bypassed by switching workspaces, using a custom domain or creating another route to the same conversation.

## Failed send or missing message

Use the provided retry action and countdown. Restore the network and inspect the conversation before manually sending duplicate text.

If outgoing messages work but incoming messages or typing appear only after refresh, check whether the browser/network blocks live connections. Reload the page and compare another browser or network. Custom-domain messaging also depends on connectivity to Biqli's central service.

A paused background tab can delay updates. Do not treat typing, online status or an open tab as proof of delivery.

## Recording does not work

Use HTTPS, grant microphone permission and check that another app is not exclusively using the microphone. Use a browser supporting recording, and stay within five minutes and 10 MB.

An empty recording, rejected format or denied permission requires a new recording. Sending text can help confirm that the rest of the conversation works.

## No reminder email

Check the verified account address, notification preference, spam folder and [delivery rules](https://learn.biq.li/help/messaging/notifications.md). Reading, activity, hiding, blocks, account availability and the conversation cooldown all affect eligibility.

Ten minutes is the initial eligibility delay, not a guaranteed arrival time. Several conversations have independent cooldowns.

## Cannot report or read an emailed conversation

Already reported content produces a toast rather than another report form. New received content may be appended to an open report.

An email link requires normal sign-in and participant authorization. Logging in as another account does not grant access. Contact support with the reference, browser, approximate time and sanitized error if the correct account still cannot continue.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.