Why a task isn't transferred
If a task in Fluo won't move, it's held by column or link conditions, a check with people, or the board workflow. Fluo shows what to do in the “To move to” window.
If the “To move to” window opened
The window opens when conditions of a column or of the link you're moving the task along hold the task. The title shows where the task is going, and the list below shows what's missing. You can do almost everything right in the window:
- “The checklist must be completed”: the window shows the same items as the task, tick them here;
- “Fields must be filled in”: a list of fields and the “Fill in the task” button. The task window opens on top with the needed fields highlighted. After you save, you're back in the move window, and the filled fields are checked off;
- “A file is required:” and a description of the file: click “Attach a file” or drag a file into the window, and it goes to the right field of the task;
- “A comment is required”: write it in the field, and it appears in the task chat;
- assignee, blockers, deadline and tags: choose an assignee or click “Assign to me,” remove a blocker with “Unblock,” pick a deadline in the calendar, add the needed tag.
Once everything is done, the “Move” button becomes available. “Cancel” leaves the task where it is. You can't bypass conditions: the project administrator sets them, see “Conditions and checks: what holds a task”.
If the task will move on by itself from the target column right away, the window also asks for the conditions of that next step up front. The title reads “For the task to move on to ‘…’,” and one comment serves both moves. If you close the window with “Let it wait,” the task lands in the column and waits there. Its card shows what it's waiting for.
If a column fades while you're carrying a card
While you drag a card, the board columns hint at what will happen to the task:
- “Will not let in:” and the reason: the column is faded with an icon, and the task won't be accepted. If you release the card over such a column, the move is canceled and the card goes back;
- “Will move on to” and a column: from here the task moves on along its route right away. Under “Needed for the move:” you see what that takes;
- “Return: the task will wait”: the task has already been there, see “How a task moves along its route”;
- “Will ask for a comment,” “Will assign you,” “Will add the check,” “Will close the task”: what the status automations and link rules will do.
Over a column that won't let the task in, Fluo shows the “Transfer is not possible” notification with the reason. For column conditions it has the “What is needed to move it?” button, which opens the “To move to” window.
A column refuses a task for one of three reasons:
- the column conditions aren't met (shield icon). Meet them in the “To move to” window;
- the board workflow doesn't allow this transition (no-entry sign). Move the task along the allowed transitions, see “Board workflow: allowed transitions within the board”;
- the column has a strict task limit and is full (lock). Free up a slot or ask to raise the limit, see “Column task limit (WIP)”.
If a check mark is pending
A column adds a check when the task enters it: a checklist item with assigned people. Until it's marked, the task won't leave for another board. Within the board, such a check holds a move along a link out of its column, but you can move the task outside the links.
The “To move to” window shows whose mark is pending.
- “You must mark it.”: tick the item right in the window. If the check asks for a comment, write it.
- “Waiting for a mark:” and names: click “Write in the chat” to call these people. The task chat opens with them mentioned.
A check doesn't stop you from returning the task. A check without assigned people doesn't hold the task.
If a task should move by itself but stays put
The task sits in a column with a “The task moves on by itself” link and doesn't go anywhere. That means something holds it.
- Look at the “Waiting:” line on the card. It shows the first reason and how many more are left. Click the line, and the task window opens on the checklist.
- Do what the task is waiting for. As soon as nothing holds it, it moves on by itself.
Right after a move, Fluo shows the “The task is waiting in ‘…’” notification. Its “What is needed to move it?” button opens the window with all the reasons.
Common reasons:
- the link asks for a comment, and the move that brought the task here had none. Move the task on by hand and write a comment;
- no branch of a fork fits the task, and there's no “Otherwise” branch. Fill in the fields so the task fits one of the branches, see “Branches: different paths by condition”;
- the link leads into a connector, and the conditions of the column where the task will land in the other project hold it. Meet them, and the task leaves by itself;
- the link leads into a connector, but the connector has no exit for the type the task gets at the exit, or the “Active connector” switch is off. There's no “Waiting:” line then. Check the “Task types at the exit” table and the connector's links, see “How to set up a connector”;
- the task was returned, see the next section.
If the task was returned
A returned task doesn't move on by itself, even if a “The task moves on by itself” link leads out of its column. Its card says “Returned: waiting to be sent on,” and the task window shows “Returned for rework, the task is waiting: send it on when it is ready.” under the route line.
Finish the task and move it on by hand. After that, the route works as usual again.
If the move menu doesn't have the column you need
Check these one by one.
- The task has a different type. Type routes don't overlap: a task sees only the links of its own route. Check the “Task type” field in the task window, see “Task types: create, choose, change”.
- The task's route has no link out of this column. If the task has a type, the task window shows “From here the ‘…’ type has no further links.” instead of the route. Links are drawn on the project's “Workflow” page, see “How to connect columns of different boards”.
- The column item is dimmed. The column is full under a strict limit, the board workflow forbids the transition, or it's a fork branch that doesn't fit the task.
- The task is completed. A completed task has no move arrow, reopen it first, see “How to complete and reopen a task”.
If rules don't run or links can't be drawn
- On the Free and Free Team plans, the workflow map is view-only: you can't draw links there.
- Status automations, link rules, conditions and checks work on the Business plan. On other plans they don't hold the task and do nothing on a move. The tooltip of the lightning bolt in the column header says “Not active on the current plan.” Checks left over from a paid plan stay in the checklist marked “does not hold the task: not active on the current plan.” A fork doesn't work on these plans either.
See “Workflows and plans”.
If a move through the API, MCP or FluoAI is refused
A move through the API or MCP goes through the same checks as in the app. The refusal lists the reasons. If a comment is needed, pass it in the comment parameter. You can't move a task through a connector into another space with the API. See “How a task moves along its route”.
Related articles
On the website: Cross-team processes in Fluo: linked boards without code