---
title: "Bisque Get work moving again"
description: "Check setup, waiting work, stale activity, and incomplete results without duplicating a task."
canonical: https://bisque.cloud/docs/factory/troubleshooting
---

# Get work moving again

Check setup, waiting work, stale activity, and incomplete results without duplicating a task.

Page: https://bisque.cloud/docs/factory/troubleshooting

Start with the task and the computer it names. Repeatedly sending the same
request can create competing work without fixing the original problem.

## Open the right account and computer

If Factory or Foreman is missing from navigation, confirm that you signed in
to the intended Bisque account. These pages depend on account access; installing
a presentation skill does not enable them. If access is still missing, report
the missing page to the person managing your Factory access.

If the page says **Factory isn't set up for this account**, follow
[Set up your first task](/docs/factory/first-task). If it says **Couldn't check this
account's Factory**, choose **Reload**. A read error does not establish that
setup is missing; do not set up a second coordinator to fix it.

If Status names another Mac as the host, use that Mac for **This Mac** controls
and local approvals. **Join Factory** on your present Mac adds a worker; it
does not repair or replace the coordinator.

## Check a Mac that is not checking in

1. Read the host name and last check-in in **Factory › Status**.
2. On that computer, check power, network access, and whether it is asleep.
3. In Bisque for Mac on the coordinating computer, check **Run in the
   background**, Foreman's sign-in, and any **Fix…** item.
4. Complete any pending Login Items approval in macOS, then check Status again.

A stale check-in is not proof that the computer or a worker has stopped.
Do not start a duplicate job or move a running job on that assumption.

## Read why a job is waiting

In Status, read **Needs you**, **Needs Foreman**, and **Waiting to start**.
A queued job needs an online computer with the right worker, repository,
tools, and available memory and CPU. A saved answer can also wait for its
assigned computer to have room to resume.

Complete a named sign-in, setup fix, or task question when it belongs to you.
For **Needs Foreman**, let Foreman handle the next step or ask it about that
specific task. Do not grant unrelated access to make a queue move.

If a job is assigned to an offline computer, restore that computer. A job
stays there; adding another worker computer does not transfer the assignment.
If you need to move it, tell Foreman whether its worker has stopped or the
computer is off before requesting reassignment.

## Distinguish assignment from activity

**Running now** shows how long ago a computer took a job and its **Last
activity** separately. The assignment's age is not the amount of time the
worker has been building. A computer's healthy check-in is not evidence that
a particular job progressed.

Open the task and read its next step and result. If the work looks stuck,
ask about that task rather than submitting its original request again:

> The README task has no recent worker activity. Check its assigned computer
> and preserve the work before deciding whether to resume or retry it.

## Check sign-in without assuming model access

If setup names a provider or coding-agent problem, open **Set Up Factory** on
the affected Mac and follow that check's fix. Bisque, model-provider, coding-agent,
and GitHub sign-ins are separate.

A setup check can confirm that a credential exists without making a model
request. **Test** sends a real request and can consume provider usage or
incur charges. Use it when you need to establish that the selected model
answers, not just to check whether you saved a sign-in.

For an installed skill that is unavailable to an agent, check the
[computer's skill report](/docs/factory/skills#read-each-computers-result), compatibility
label, and whether the agent session started before installation.

## Report a result that is still wrong

If the task links a pull request but the app has not changed, ask which
release or installation step remains. Merging alone does not establish that
the change reached you.

For an incorrect document or behavior, reply on the task when it offers a
reply field, or name the task in Foreman chat. Include what you expected and
what you saw. A delivery-closed task can reopen when you explain what is
missing.

## Give Foreman enough context to investigate

Send the task name or link, the affected computer, the visible message, and
what happened immediately before it. Include the installed app version if the
problem differs between computers. A screenshot can show a missing control
or error; remove private information before attaching it.

Do not post API keys, provider tokens, complete conversation histories, or
unrelated project files. Ask Foreman which additional diagnostic information
it needs rather than uploading everything.
