When a mission cannot start

Read the requirement first#

Start with the specific requirement Kite shows. Setup, permissions, connection readiness, funding and usage limits describe different problems. Resolve the named requirement before trying again.

Keep the mission objective and selected audience in view. A technically ready mission still needs the right people and useful required criteria.

Check your setup#

Review the business or product context, the mission's selected people, saved messaging and the sender or channel connection relevant to the work. If you use a Kite email, you avoid building personal email infrastructure, but sender confirmation and the relevant setup controls still apply.

Work through one requirement at a time: read what is missing, open the relevant setting, complete the required step, return to the mission and review again.

One requirement at a time

Resolve the blocker, then review your mission again.

1. Read the requirement2. Resolve the named requirement3. Return to review

Step 1 of 3

Read the requirement

Identify the specific setup or permission Kite asks you to review.

Next step

Check your control settings#

Confirm the configured permissions and review/start controls. Paid availability of Run it does not activate work or override saved involvement settings. Free is excluded from Run it.

Do not solve a permission hold by granting authority you do not want Kite to have. Choose the settings that fit how you want to work, then review the actual mission within those settings.

Check the relevant resource#

Reach, active capacity and credits are separate. Read the requirement tied to the blocked action rather than assuming one balance explains everything. If Kite asks for funding or a plan action, review its actual terms in the product before proceeding.

Check current balances and requirements in your Kite workspace.

Ask for help with context#

If you cannot resolve the requirement, contact Kite support. Include the mission, the message you see and the step you already tried. Share only the information needed to diagnose the issue. Do not include passwords, private keys or full payment details.