A Bandmate cannot start or resume

Find why a delegated assignment cannot begin or continue.

Before you start

Open the lead that owns the assignment. Keep the failed assignment and its report so you can distinguish a new failure from an earlier attempt.

Open the affected assignment inside its lead before diagnosing a failure. Its brief and activity identify the exact work and provider involved.

Step by step

1. Open Band and select the affected assignment. Read its brief, current state, and latest provider error.

2. Check whether it is waiting on another assignment or a concurrency limit. Waiting for a dependency is different from a failed launch.

3. For a saved Bandmate, check Settings → Band: the profile must be enabled and its provider configuration must be usable.

4. For a permission or MCP startup error, inspect the named policy or tool. Increasing concurrency will not repair an authentication or permission failure.

5. Correct the identified cause, then use the explicit Resume action for stopped work when available. Opening the panel alone does not resume it.

6. Read the resumed activity and the lead’s integration result. Ask for a bounded revision if the specialist completed only part of the brief.

What to expect

You can distinguish scheduling, profile configuration, provider errors, and explicit pauses before retrying.

Troubleshooting and useful details

Turning Delegation off prevents new runs but is not the control for stopping an existing team. Do not broaden access solely to silence an unexplained error. A failed assignment is not successful integration, even if another Bandmate finished.