Communication history
See when ReminderStream received your messages and which saved events resulted. This is incoming history; outgoing reminder delivery is shown on each event.
Retained receipts expire 30 days after their latest processing record. Choose a channel to browse dates and saved events. Times are shown in UTC; they are not the sender’s original send time.
AI may miss an event or its date. School notices and other messages may be informational. No events found means no events were identified by processing; it does not prove the original message has no event. Check the original message and create a reminder manually when you know the date. A processing failure is a separate outcome, and only confirmed saves appear as reminders.
This is partial application history. Saved-event links require a confirmed save. Some failed or older activity is missing. Provider retries are not counted as new communications.
What is recorded and what processing status means
Valid new text-analysis requests appear here when received, including a safe rejected or failed outcome if processing ends before events are saved. Saving a suggestion links its event to that preview. Verified text messages that reach processing are recorded, including menu, schedule and acknowledgment replies, plus stop, restart and help requests. Analysis and its incoming text share one visible receipt; proven saved events link to the original analyzed message. Assistant/API entries cover newly recorded analysis requests, including requests without a supplied source ID, from the date this history is enabled. Your assistant/app must preserve the returned reference when saving a suggestion to link the event here. The receipt time is when the first analysis request reached the app. Texts that fail identity or consent checks, some failed requests, older activity and unrecorded legacy deliveries are not included yet. A separately received identical email reuses earlier processing and existing saved events; a provider retry retains its original receipt. Processing finished means the handler returned, not that a reply was delivered or a requested change was saved. A text command receipt is an application record, not confirmation of reply delivery or carrier recovery. Unsaved suggestions are never shown as created events. Older receipts may not include attachment preparation counts; absence of counts does not confirm that files were analyzed.