Skip to main content
Find the symptom, check the causes in order.

Briefings

The Co-founder is part of the Startup plan and higher. On other plans the section shows a preview with an upgrade prompt. A subscription that is past due or canceled also loses access until it is active again.
Check these in App Co-founder → Settings:
  1. General → Co-founder enabled is on.
  2. General → Apps: the app is turned on. It only appears there once it is marked Live in My Apps.
  3. You are within your plan’s app limit (Startup: 3 apps). Apps past the limit do not run.
  4. Schedule → Days: at least one day is selected. With no days, scheduled briefings are off.
  5. Schedule → Proactive mode is not Event only. That mode turns the daily briefing off.
  6. Schedule → Timezone is your own. The time is read in that timezone.
If a briefing failed, it is tried again later the same day, within about six hours of the scheduled time. Look under Reports before you assume it is missing.
You can start one briefing per app every 24 hours by hand (RUN_COOLDOWN in the API). Wait, or read the latest one under Reports.
An app in development has no production data, so briefings are blocked for it (APP_NOT_LIVE in the API). Mark it Live in My Apps.
The Co-founder only has those numbers when App Store Connect or Google Play Console is connected.If App Store Connect is connected and numbers are still missing, check the role of your key. Only a key with the Admin role can read sales, analytics, reviews and in-app purchases. The briefing names the part it could not read.Store data also arrives with a delay. When the latest days are not in yet, the briefing says how fresh the data is instead of reporting a drop.
  • RevenueCat numbers cover the whole RevenueCat project. With several apps in one project they are project totals, not one app’s revenue.
  • Meta Ads numbers only include campaigns that promote this app, so they can be lower than the ad account total.
  • Leave revenue out in Settings → Agent removes revenue from briefings completely.
Set Briefing language and Briefing length in Settings → Agent. With Auto, the language follows your locale.
With two or more apps, email and Telegram send one digest. Turn on Separate email briefing or Separate Telegram briefing for an app in Settings → General → Apps.

Actions

  • An action is only created when a connected integration can carry it out. Connect App Store Connect, an ads network, Linear or GitHub, depending on what you want it to do.
  • At Autopilot level 0 no actions are created. Set it to 1 or higher.
  • Recommendations that nothing can act on stay in the briefing as prioritized actions.
You approved it, but applying it failed. The card shows the reason. Common ones:Some action types are retried for you. See Automatic retries.
  • It was not proposed again for 14 days and became Superseded.
  • A newer proposal for the same thing replaced it.
  • It was set to run automatically and hit a connection problem. Check Connection health in Integrations. It is proposed again after you reconnect.
Use the status filter in Actions, or Decisions, to find it.
  • Check that Agent mode is Write. In Read mode nothing runs without approval.
  • Check Autopilot level: issues need level 2, App Store metadata needs level 3.
  • Ads changes, monetization changes, win-back campaigns, UGC clips and social comment replies always wait for you.
  • A Require approval policy rule overrides autopilot.
  • A metadata change that would drop a top-20 search term always waits for you.
A rejected idea is only proposed again when new evidence changes the case. To stop a recommendation for good, say “never recommend this again” in Slack or Telegram. To bring a rejected action back, use Move this back to Pending.
The proposed metadata would remove a word that a top-20 search term needs. Approve only if you accept losing that rank, or ask in chat for a version that keeps those words.

Alerts and routines

Check, in order:
  1. Send alerts is on, and Alerts per day is not 0.
  2. Proactive mode is Mixed. Alerts are not sent in Off or Event only.
  3. The event reached Alert me for (High and critical by default).
  4. It was not inside Quiet hours. Non-critical alerts wait until they end.
  5. You were under your daily limit.
  6. Your briefing was not due within 90 minutes. In that case the briefing covers the event.
  7. No other alert for the same app went out in the last hour.
The Co-founder also stays quiet on purpose when it finds the event is noise or something you already explained. The event still shows on the Signals page and in your next briefing.
Alerts go to Telegram and the mobile app when they are connected, and to email otherwise. Pair Telegram in Integrations, or install the Appeeky mobile app.
A routine that fails three times in a row is paused. Open its history to see the error, fix the cause (often a missing connection), then resume it.
A run is skipped when the master switch is off, your plan is not active, the app was removed from My Apps, or you reached 24 routine runs in a day.
With only when something needs you, a run that finds nothing stays quiet. Open the history to see what it checked, or switch the routine to notify on every run.
You are running the Co-founder on your own Mac in the desktop app. Routines run in Appeeky cloud only. Switch Where it runs to Appeeky cloud to use them.

Chat

Ask “Which integrations are connected?” to see what the Co-founder can reach. Data sources are connected in the dashboard Settings; Slack, Telegram, Linear, GitHub and Notion in App Co-founder → Integrations.
The Co-founder picks up these areas from the wording of your question. Name the topic: “my Apple Ads campaigns”, “ChatGPT visibility”, “our SEO and backlinks”, “our UGC creator”, “Reddit opportunities”.A bare “keyword” or “ranking” is read as an App Store question. For Google rankings, say “SEO”, “Google” or “website”.
In read mode the Co-founder never changes anything directly. It queues the change with Approve and Skip. Switch Agent mode to Write if you want it to act when you tell it to.
  • The bot only works in a private one-to-one chat, not in groups.
  • If the chat is not paired, send /start and use the pairing link from Integrations → Telegram.
Turn on Post daily brief to Slack in Settings → Delivery, pick a Briefing channel, and invite the bot to that channel.

Missions and coding agents

  • An app can have only one open localization mission. Finish or cancel the open one first.
  • Without a list of locales, the Co-founder picks markets from your download data. If no unlocalized market stands out, there is nothing to propose. Give it the locales yourself.
The card shows the step and the error. Fix the cause, usually the App Store Connect connection, and choose Retry. Steps that already finished are not repeated.
A Hermes or OpenClaw gateway must be reachable at a public HTTPS address. Private and local addresses are rejected. The connection is tested when you save it; if the test fails, check the URL and the key.
You can start up to 10 coding agent tasks a day and have 3 running at the same time. Wait for a running task to finish.

Desktop app, running on your Mac

On This Mac the Co-founder needs your own model API key. Add it in Settings → Model. Scheduled briefings also only run while Appeeky is open.