Troubleshooting

The ten things that trip people up — and how to fix them.

1. My report says 'no data' even though I have activity.

   Likely cause: Usually a date-range mismatch — the prompt references last week but your source's events happened today.

   Fix: Check the timestamps in your source and compare to the placeholders in your prompt. See the prompt placeholders doc.

2. Run failed with 'rate limit' from GitHub / Linear / Slack.

   Likely cause: The provider rate-limited the token. We retry 5 times with exponential backoff.

   Fix: No action usually needed — the run will succeed on a retry. If it persists, stagger two reports that share a token, or upgrade the provider's rate limit tier.

3. Scheduled run fired at the wrong time.

   Likely cause: Your account timezone may be different from your calendar expectation.

   Fix: Check Settings → Profile → Timezone. Schedules are interpreted in this timezone. Switching timezones reschedules existing reports.

4. Slack post missing from the channel.

   Likely cause: The AutoReport app isn't invited to that channel.

   Fix: In Slack, run /invite @AutoReport in the destination channel, then hit Run now to confirm.

5. Webhook endpoint isn't receiving requests.

   Likely cause: Signature verification failing or the endpoint isn't reachable.

   Fix: Use the Send test button in the dashboard — the response is shown verbatim. Double-check that your endpoint accepts POST and responds in < 10s. See webhook docs.

6. Output is too long or too verbose.

   Likely cause: The prompt doesn't cap length or specify tone. The model defaults to long.

   Fix: Add explicit guardrails in the prompt: “In under 200 words, use bullets, keep tone brisk.” Small changes in the prompt drive large changes in output.

7. Report references data I don't have access to.

   Likely cause: The prompt implies data that isn't in the connected sources. The model can hallucinate dependencies.

   Fix: Ground the prompt in your sources: “Only use data from GitHub.” or remove unrelated placeholders.

8. OAuth reconnection loop.

   Likely cause: Your token was revoked in the provider.

   Fix: Go to Sources → Reconnect. If you keep getting redirected, make sure your provider account has the scopes listed in the consent screen.

9. Run quota exhausted.

   Likely cause: You've hit your plan's monthly report or manual-run limit.

   Fix: Upgrade on the pricing page or pause one of your reports. We never charge overage without you picking a plan.

10. Something else weird is happening.

    Likely cause: The AutoReport team, probably.

    Fix: Email support@autoreport.to with the run ID. We aim to reply inside one business hour.