Troubleshooting
Common problems and how to solve them, grouped by what you were doing. Each entry is titled with what you see, says why it happens and what to do, and links to the article that explains it in full. If your problem is not here, contact help@floxar.com.
Signing in
Floxar shows "Verify your e-mail address"
Why: your sign-in provider has not confirmed your email address yet.
What to do: verify the address with that provider, then sign in again. See Signing in and authentication.
Sign-in says it is temporarily unavailable
Why: a short-lived problem on Floxar's side. Nothing is wrong with your account.
What to do: try again in a moment.
You can sign in but no longer see your account
Why: an administrator of that account has probably deactivated your membership.
What to do: contact an administrator of the account; only they can restore your access. When you return, you have basic membership, and roles you held before must be granted again. See Inviting users, roles, and permissions.
Signing up is blocked
Why: many sign-ups were attempted from the same network in a short time.
What to do: wait a while and try again.
Finding content
A flow, bit or reference you expect is not in the list
Why: lists show the content of your working context, the account, organization or group you have selected. Content belongs to exactly one of them and never appears in another.
What to do: switch your working context to the organization or group the content belongs to. If you cannot select it, you do not have access to it yet; ask an administrator. See Organizations, groups, and scopes.
You can see the account but nothing in it
Why: you are a Member without a role. A Member belongs to the account but cannot see or do anything until a role is granted.
What to do: ask an account administrator to grant you a role. See Inviting users, roles, and permissions.
The options to edit a flow or bit are missing
Why: editing needs edit permission, and the actions are hidden from people who do not have it.
What to do: ask an administrator for edit permission on the account, organization or group the content belongs to.
Running trails
You cannot move to the next step or complete the trail
Why: the step has required elements that are not answered yet. Floxar shows which ones are missing.
What to do: answer them, then move on. Pausing, handing the trail over and abandoning it are never blocked. See Interactive elements and their settings.
A next-step card says "Available when …" and cannot be chosen
Why: the connection depends on an answer on this step, and that answer has not been given.
What to do: give the answer the card names, for example the option it asks for, and the card becomes available. See Bit connections.
The trail you were working on was paused
Why: you work one trail at a time. Starting or resuming another trail pauses the active one, including a trail that your AI client starts for you.
What to do: resume it from your Worklist. It keeps its place and its answers. See Running and tracking trails.
A trail's answers are read-only
Why: answers can be changed only on an active trail that is assigned to you. A paused, queued, completed or abandoned trail, or one assigned to someone else, is shown read-only.
What to do: resume the trail, or claim it from the queue, to work on it. A completed or abandoned trail can be reopened with a reason.
Building content
You cannot archive a flow's start bit
Why: an active flow must always have a starting bit.
What to do: make another bit the flow's start bit, or deactivate the flow, then archive the bit. See Building flows.
You cannot archive a reference
Why: bits still link to it.
What to do: open the reference to see the bits that use it, remove those links, then archive it. See References and the process library.
A new organization or group name is refused
Why: names must be unique among neighbours: two organizations in the same account, or two groups in the same organization, cannot share a name.
What to do: choose a different name. See Account settings and administration.
AI clients
Your AI client cannot connect, or stopped working
Why: the sign-in page or the client says why, for example that the account does not accept the client, or that your sign-in expired.
What to do: find the message in Connecting an AI client to Floxar, which lists each one and its fix.
Your AI client cannot do something you can do
Why: a connection has only the capabilities you allowed when connecting, and your role in the account limits it further.
What to do: reconnect and allow more, or ask an account administrator about your role. See Connecting an AI client to Floxar.
Last reviewed: 2026-10-06