DEV Community

Manuel Bruña for APX

Posted on

Test your AI assistant's calendar reminders before relying on them

APX is a free, open-source desktop app that runs your own team of AI agents on your machine.

Connecting a calendar is not the same as getting a useful reminder. The event can be visible to the assistant while reminders are disabled, held by quiet hours or sent somewhere you are not looking.

Before relying on a reminder for a real meeting, run a small delivery test. This is a proposed checklist, not a report of a test performed on your account.

1. Write down the delivery contract

Use a sentence with four concrete parts:

For a timed event on my connected work calendar, remind me 30 minutes before it starts, on my private notification channel, outside my quiet hours.

Then check whether the actual settings match that sentence. Include the time zone. If you need time to travel or prepare, choose the lead time for that work rather than for the moment the meeting begins.

Keep the destination private unless everyone in a shared room is allowed to see the event's title, location and meeting link. Reading your calendar and disclosing its contents to a group are different decisions.

2. Know which events qualify

The current APX integrations documentation puts Remind me of my events under Configure integration on the Google Calendar integration. It is off until enabled.

The documented behavior matters when designing your test:

  • The default lead time is 30 minutes; it can be set from 5 minutes to 7 days.
  • Calendar checks default to every 5 minutes, with a configurable interval. APX keeps that interval no longer than the lead time.
  • All-day events and declined invitations are excluded.
  • Quiet hours hold reminders until they end.
  • An event is announced once, but moving it can cause another announcement.
  • Events you muted are not announced.

The reminder check itself does not call a model. That does not mean every calendar task or connected service is free: asking an agent to reason about your schedule is a separate activity.

3. Test an ordinary event first

Create one harmless, timed event on the intended calendar. Leave enough time for the configured lead time and a calendar check. Do not add guests: invitations introduce another external action and are unnecessary for this test.

Record what you expect before waiting:

Check Expected evidence
Account and calendar The test event is on the connected calendar you intended
Event time The displayed time and time zone match your plan
Lead time The notice arrives early enough to act
Destination The actual message appears where you expect to receive it
Content The event, time and location or link are correct

Read the delivered message. A saved setting, a successful calendar read or an assistant saying 'reminders are enabled' is not delivery evidence.

If quiet hours matter to your schedule, test that boundary separately. A notice held until morning may behave as documented and still be too late for an early appointment. Decide whether that configuration fits your needs.

4. Diagnose a missing notice without making duplicates

Start with the connected account, event eligibility, reminder switch, lead time, muted-event list, quiet hours and notification destination. Do not immediately create a second copy of the appointment. That adds noise without explaining the first failure.

Also distinguish a missing message from an intentional second notice: the documentation says a moved event can be announced again. Compare the event's current time before treating that as a duplicate-delivery bug.

A useful acceptance note is short: which event was tested, which settings were active, where the notice arrived and what remains untested. One successful test is evidence for that setup, not a guarantee about every future event.

This article expands on APX's calendar-reminder guide with a delivery contract and an acceptance table. For a broader look at the assistant's workflow across chat and meeting notifications, see the official APX v2 overview video (Spanish); it is an overview, not proof that your calendar is configured correctly. Explore APX and check the current integration settings before depending on them.

Top comments (0)