Unindexed server events

What to do

• Check whether you use FullStory API in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2024-09-12 20:02 UTC and 2024-09-12 20:02 UTC may need a replay.

• Subscribe to FullStory's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=fullstory works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from FullStory 1

1. resolvedSep 12, 2024, 8:02 PM UTC

   Starting on March 26th, as a result of processing optimization improvements, a bug was introduced that resulted in some server events for some accounts not being properly indexed or sent to data warehouses. We were made aware of this issue on September 11th and released a fix on September 12th. All server events after the fix was released have been properly indexed and sent to data warehouses, where applicable. All server event data was captured, and no event data has been lost, but server events may appear missing in session replay. If you are missing server events between March 26th and September 12th and would like for us to reindex them for your account, please reach out to support@fullstory.com. Note, reindexing will not send updates to data warehouses. Specific situation where server events were impacted: Sessions containing multiple server events sent via Server API may not have all of their server events processed, indexed and warehoused. When a session receives events and are placed into a new page, that page is processed immediately. When subsequent events are received with timestamps that are not later than the previous server events, the processed for that updated page is skipped since no new data is detected. As a result, server events may appear missing if their timestamp was not later than the prior events and those events were received after those prior events had been processed.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.