Fictura
Events

Problems with incoming events

What Fictura refused, ignored or flagged when your app sent events, counted per type with the latest example.

Dashboard → Events → Manage → Problems with incoming events. One row per kind of problem over the last 7, 30 or 90 days: how many times it happened, when it was last seen, and the latest example (masked until you press Show samples, since an example can carry a device id or an event's properties). Counts are written in batches, so the last minute may not be in yet.

Saved means the event was stored anyway; not saved means it was lost. The type below is shown in small print under each row's plain name.

TypeSaved?What happened
unplanned_eventsavedThe app has declared events, and this one is not among them.
missing_required_propertysavedA declared event arrived without one of its required properties. The sample names the key.
wrong_property_typesavedA required property arrived with another type than declared. The sample names the key.
name_casingsavedThe name mixes upper and lower case (tool_paywalls_ON). Use lower snake_case.
illegal_identifiersavedAn id like guest, null or 0 was ignored when matching the user.
clock_skew_ignoredsavedThe device's clock order was impossible (sent_at before an event's timestamp), so times were not corrected.
merge_refusedsavedTwo users with different account ids were not merged into one.
client_dropped_reasons_invalidsavedEntries of the batch's client_dropped_reasons were ignored.
invalid_session_idsaved$session_id is not a UUID v4 or v7, so the event is grouped into a session by idle gap instead.
attribute_droppedsavedA user attribute key or value broke the limits (100 keys, lower-case letters, digits and _ up to 40 characters, strings up to 1,024). That attribute was ignored; the rest applied.
pii_redactedsavedEmails, phone numbers or IP addresses in property values became [redacted], under the app's privacy setting. The sample names the keys.
suppressed_identifiernot savedThe batch or billing webhook carries an identifier of a deleted person. The sample names the identifier types, never the values.
invalid_namenot savedThe name is empty, longer than 200 characters, or has control characters.
reserved_namenot savedNames starting with $ are reserved for Fictura.
invalid_eventnot savedThe event, or its properties, is not an object.
too_many_propertiesnot savedMore than 255 property keys.
too_largenot savedProperties over 64 KB once serialized.
no_valid_identitynot savedThe request had no usable device, account or RevenueCat id.
device_throttlednot savedOne device sent more than 600 events in a minute; the excess was dropped.
client_dropped:<reason>not savedThe SDK dropped events on the device before sending (a full queue, for example) and reported how many.

The tracking-plan checks (unplanned_event, missing_required_property, wrong_property_type) only run once the app has at least one declared event. Nothing is ever dropped for them.

Each batch's own answer says the same thing per request: see failed, throttled and warnings on Ingest events.