Event limits and retained events

Free includes the first 100 readable events per workspace each UTC calendar month, shared across its projects. NativeWatch then accepts up to 400 additional locked events, for 500 accepted events in total. An event is an error occurrence or an activity entry, such as a request or query. Several occurrences can belong to one issue.

#What happens after 100 events

Additional events appear as locked placeholders with a type and timestamp. Select a placeholder to see the upgrade prompt. Their messages, stack traces, source, user information and activity details are not sent to your browser or exposed through search, emails, AI or MCP.

Locked events remain private for up to seven days. The prompt shows when the oldest retained event expires. Activity retention follows its occurrence timestamp, capped at seven days after acceptance, so a delayed activity can expire sooner. Error retention begins when NativeWatch accepts it.

#Unlock retained events

A workspace owner can open Settings → Billing, choose Indie or Pro and complete Stripe Checkout. Returning from Checkout does not unlock data on its own. NativeWatch waits for a verified active subscription from Stripe.

After confirmation, unexpired locked events become readable in their original projects. They keep their original event IDs and timestamps and do not consume quota a second time. Historical errors do not produce a backlog of notification emails. Expired data cannot be recovered by upgrading.

An upgrade increases the current month's allowance without resetting accepted usage. Events unlocked by a paid subscription remain readable after a later downgrade, subject to the current plan's retention. New events follow the current plan's allowance.

#Capacity, retries and the monthly reset

After 500 accepted events on Free, further submissions receive HTTP 429 with code: event_quota_exceeded. Activity batches are accepted or rejected as a whole at this capacity boundary. There are no automatic overage charges. Paid plans reject submissions after their displayed monthly allowance.

The server deduplicates retried error occurrences by project and event UUID. Replaying an accepted error does not consume another slot. Activity entries currently have no event UUID and do not have the same retry deduplication guarantee. See offline delivery for SDK queue limits and retry behavior.

The allowance resets at the beginning of each UTC calendar month, independently of the subscription billing date. A new month does not unlock the previous month's retained events or extend their expiry. Deleting or expiring an event does not refund its usage slot.

#Usage emails

Verified workspace owners can enable usage emails in Settings → Notifications. Notifications at 75% and 100% refer to the readable allowance. On Free, the full-limit email explains the additional private buffer and its expiry. It does not mean all 500 slots have been used.