Scheduled Report Missing
Fix alice scheduled reports that are not posting to Slack channels on time
Scheduled Report Missing
What You See
You set up a scheduled report on a skill, but the Slack channel never receives the message at the expected time.
Quick Fix
Invite alice to the channel. In the Slack channel where the report should post, type:
/invite @alicealice must be a member of the channel to post scheduled messages. This is the #1 cause of missing reports.
Detailed Diagnosis
1. Check the Schedule Trigger Status
- Go to Dashboard > Skills and click on the skill
- Look at the Triggers section
- Verify the Schedule trigger shows as Active (not paused)
- If paused, toggle it back on
2. Verify Channel Membership
alice can only post to channels where the bot is a member:
- Public channels -- alice must be invited with
/invite @alice - Private channels -- alice must be invited by a channel member
- DMs -- alice cannot post to DMs on a schedule (only on-demand via slash commands)
3. Check the Timezone
Cron schedules are interpreted in the timezone set on the skill. If your report is set to 0 9 * * 1-5 (9am weekdays) but your timezone is wrong, it will fire at the wrong time.
- Open the skill in the builder
- Go to the Schedule step
- Verify the timezone matches your local timezone
- Common issue: timezone defaults to
UTCif not explicitly set
4. Check Your Plan
| Plan | Scheduled Reports Allowed |
|---|---|
| Free Free | 1 (weekly frequency only) |
| Pro Pro | Unlimited |
| Business Business | Unlimited |
On the Free plan, only one scheduled report is allowed, and it can only run on a weekly schedule. Daily or hourly schedules require Pro or Business.
5. Check the Query Limit
On the Free plan, scheduled reports count toward the 50-query monthly limit. If you have exhausted your limit, reports are silently skipped until the next billing cycle.
Go to Settings > Billing to check your current usage.
6. Check the Logs
The most reliable way to diagnose is through logs:
- Go to Dashboard > Logs
- Filter by the skill name and trigger type "cron"
- Look for recent entries:
- Success but no Slack post → channel membership issue
- Error with
CHANNEL_NOT_FOUND→ the channel was deleted or renamed - Error with
RATE_LIMITED→ plan limit exceeded - No log entry at all → trigger is paused or timezone mismatch
7. Source Connection Issues
If the underlying source has disconnected since the schedule was set up, the report will fail:
- Go to Dashboard > Sources
- Check for any Error or Disconnected status
- Reconnect the source if needed
Still Stuck?
Email support@alicehasnoidea.com with the skill name, the expected schedule, the target channel name, and a screenshot of Dashboard > Logs filtered for that skill.
Was this page helpful?