Troubleshooting
Recover a connection, find missing work and check an uncertain action without duplicating it.
Messages in forms and settings
Read the message and its action before continuing. Information messages use a muted green-grey background; success messages use soft green. Warnings use amber and errors use pale red. Each also has a distinct icon, so you do not need to rely on colour alone.
A success message applies to the step it describes. For example, an accepted tutorial email still needs to be imported into Seflo. If a message offers Reconnect, Try again or Open settings, use that action to address the stated problem. After an uncertain send or handoff, check the existing operation instead of submitting a duplicate.
The AI assistant cannot find my task
- Open the task in Seflo and copy its actual code or link.
- Check that the AI client is connected to the same Seflo account.
- Select or enable Seflo in the current conversation.
- Ask it to read that exact task before attempting changes.
If a search returns several matches, select the correct one. If no task exists yet, follow Getting started or the relevant source guide.
My source is connected but no tasks appear
Check the connector's import rules. Slack, Teams and Mattermost use explicit message selection. Project tools usually require selected boards, Lists or projects and work assigned to the connected user. Gmail stars and Outlook flags import only when their automatic import setting is enabled.
Verify one eligible source item and its connection settings. Connecting the account alone does not mean that every item will become a task. If the source reports synchronization or discovery problems, resolve those before widening the scope.
I connected the wrong account
Compare the mailbox, workspace, tenant, organization or verified worker shown on the source page with the original item. Reconnect using the intended identity. Check the resulting account before preparing an external reply.
For AI connections, reconnect Seflo using the login that owns your tasks. Your provider login and Seflo login serve different purposes.
An attachment is missing or still importing
Open the task's file area and inspect the status. Verify that the connected source account can still open the original file. Wait for an active import, or follow its error guidance. An AI-generated local file must be saved to Seflo or attached to the action before it can be sent. See Work with files.
A reply or completion action is unavailable
Read the specific reason. The source may have changed, the record may be closed, the account may have lost access or the task may have no source. For mapped project tools, check whether the configured destination still exists and the current source state permits that transition.
Refresh the context and reopen the review after resolving the issue. Do not substitute a public reply for an internal note, or a different recipient for the intended one, just to make an action available.
I am not sure whether my reply was sent
- Open the existing review or operation result.
- Inspect the original conversation for the intended message and attachments.
- Follow the existing operation's recovery instructions if it is still running or partially complete.
- Create another send only after establishing what happened to the first one.
See Review and confirm actions for the distinction between a prepared draft, an operation and personal task completion.
I cannot see the review inside my AI client
Follow the Seflo review link and sign in with the same account. Review the destination, text and attachments in the browser. If there is no link, ask the assistant to open or return the review for the prepared action rather than prepare another send.
A video will not play
Use the Watch … on YouTube link below it, or follow the written steps in the article. The embedded player loads only after you select Load YouTube player.
What to include when reporting a problem
Record the connector or client, the time, the step that failed, the visible error and the task or operation link. Omit passwords, access tokens and unrelated conversation contents. This gives the person investigating enough context to locate the failure without sharing your credentials.