# Troubleshoot generating with MockFlow Bridge > Fix problems when Mida runs on your own agent: nothing appears on the board, the agent is still working, timeouts, file access, connected tools, daily limits and AI credits. Source: https://mockflow.com/docs/troubleshoot-generating-with-mockflow-bridge When your board is connected to MockFlow Bridge, Mida and the AI on each item run on your own agent. If a request does not draw what you expect, find the message or symptom below. If the board is not connected at all, see [Troubleshoot pairing your board with MockFlow Bridge](/docs/troubleshoot-pairing-mockflow-bridge). ## Nothing appears on the board - **The board tab is not in front.** Bridge draws on the board you are looking at. Keep the board's tab open and in front while your agent works. If several boards are connected, your agent may ask which one to use; open the one you want. - **The agent replied in text only.** Ask again and say where the result should go, for example "Draw it on the board as a flowchart". - **"The local agent finished without drawing anything on the board."** The agent ran but did not draw. Send the request again, or describe the result more specifically. - **"The agent called its board tools, but none of the calls reached this board."** Your agent drew into a different MockFlow connection, such as a second copy of Bridge or a MockFlow connector added directly to the agent. Close other copies of Bridge, and remove other MockFlow connections from the agent's settings, then try again. - **"The agent tried to use ... but the call never reached this board."** Your agent's own app asked for permission to use a MockFlow tool, which cannot be shown while Bridge runs it. Run the connection command from the box Bridge shows when it starts, keeping the connection name **mockflow**, then restart Bridge and try again. - **"No reply and no board calls arrived from Gemini CLI"** (or Cursor CLI). These agents must be connected to Bridge once. Run the command shown in the message, or in the box Bridge shows when it starts, then try again. ## "The local agent is still working on the previous message" Each board runs one request on your agent at a time. Wait for the current reply to finish, or stop it, then send the new message. Messages such as **A component is already generating on this board** and **A board plan is already generating on this board** have the same cause. ## "The local agent timed out" AI on an item, such as generating a mind map or changing a chart from its toolbar, has two minutes to finish on your agent. If it takes longer, MockFlow AI generates the item instead, using AI credits. Large requests on a slow model are the usual cause; try a smaller request or a faster model. ## "Lost connection to the local bridge" The board lost its connection to Bridge while Mida was answering, usually because the Bridge window was closed, the computer went to sleep or Bridge restarted. Start Bridge again if needed, check that the strip in Mida reads **Connected**, and send the message again. ## Mida says it cannot read your files ![The MockFlow Bridge terminal showing the warning box File access is OFF: Mida cannot read any files on this computer. To let it read one folder, restart with mockflow-bridge --workspace followed by the folder path](https://assets.mockflow.com/docs/media/da41c13ab2024254a040f90dadcdf716.webp) Bridge reads files only from a folder you share when you start it. If its window shows **File access is OFF**, stop Bridge and start it again with the folder: ```bash mockflow-bridge --workspace ~/Projects/your-project ``` Reading local files is part of Bridge Pro. On Basic, your agent cannot read the folder even when you start Bridge with `--workspace`. Attaching a single file to a message in Mida works on every plan. See [Let MockFlow Bridge read your local files](/docs/let-bridge-read-your-local-files). ## Connected tools such as Jira or Slack are not used - **"Connected sources ... are a Pro feature."** Your agent can read connected tools on Max. - **No connected tool is applied.** Open **Connections** in Mida and apply the tool you want to use, then ask again. ## AI credits were used while connected Media items, such as AI images, video clips, sound and 3D models, can only be generated by MockFlow AI. When you ask for one, Mida tells you that it runs on MockFlow AI and uses your AI credits. AI on an item that times out on your agent is also generated by MockFlow AI. Everything else your agent generates uses no credits. ## "Free generations used up for today" On Basic, Bridge includes a daily number of free generations. When they are used up, Mida replies that you have used your free local agent generations for today; they reset the next day. Plus and Max have no daily limit. See [MockFlow Bridge on each plan](/docs/mockflow-bridge-on-each-plan). ## "The board could not be generated" A board plan could not be drawn. The message ends with the reason when there is one. - **None of the planned components were drawn**: try the plan again, or choose fewer items. On Windows, a very large plan can be too long to pass to the agent; split it into smaller plans. - **The local agent stopped before finishing some items**: the items that finished are on the board. Ask Mida for the missing ones. ## The reply or the drawing is not what you asked for Results depend on your agent and model. Some agents send their reply in one piece at the end, and some cannot search the web. If one agent struggles with a kind of request, try another with `mockflow-bridge agent`. See [Choose the AI behind MockFlow Bridge](/docs/choose-the-ai-behind-bridge).