things-reminders-manager

To prevent duplicate reminders in Things, use a duplicate handling policy like update-first or ask-first to catch existing tasks before creating new ones. This avoids accidental repeats when rescheduling or adding reminders.

Setting Things reminders with relative dates requires resolving the current local date and time, then normalizing the phrase into an absolute schedule. The Skill applies configurable timezone settings to return a confirmed absolute date and time.

Yes, you can override the timezone when creating Things reminders by applying configurable timezone settings. The Skill resolves the current local time and normalizes the schedule to ensure the reminder fires at the correct absolute hour.

The best way to update an existing Things reminder without creating a duplicate is using an update-first mutation path. This deterministic workflow checks for existing tasks and modifies them instead of blindly adding new ones.

Things reminders fail with relative dates when the current local time is not resolved correctly. The Skill fixes this by resolving the local date, applying timezone overrides, and validating authentication before returning an absolute schedule.

Yes, you need authentication to correct Things reminder date errors. The Skill uses an auth-aware update path that blocks or prompts the user when token access is missing to ensure secure deterministic mutations.