A Mode 2 upload (JSON, CSV, or Parquet) can store events without writing a Work-Input or Work-Output series. That is expected when the account is missing a matching enabled field mapping, a matching Asset Profile, or both.
Those events are not lost forever. They also do not fill a series on their own later.
The file is parsed and counted against the daily ingest meter. Kept events can appear in Historical Metadata. The upload result may list unprofiled Asset ids — names seen in the file that are not yet Asset Profiles.
A series is written at upload time only when all of these are already true for that event:
1. At least one enabled field mapping matches the event and can extract a Work-Input or Work-Output value.
2. The mapping can resolve an Asset id (usually from the event’s Asset field).
3. That id already exists as an Asset Profile. Upload never creates Assets by itself.
If there is no enabled mapping, events can still be accepted. If a mapping matches but the Asset is not in the catalog, events can still be accepted. In both cases, that batch does not touch a series.
Suggesting a mapping, or turning a mapping on later, does not walk old events. Creating an Asset by hand on Asset Profiles also does not replay stored events.
Use Create profile on the unprofiled list in the upload result or on Historical Metadata. That creates the Asset (Test lane by default) and replays enabled mappings onto up to 500 of the most recent visible stored events for that id.
If the Asset already exists, the same action replays only — it does not skip because the Profile is already there.
Order matters:
· Create or enable the mapping first, then Create profile, if you want those stored hops on the series.
· Create the Asset first (or Create profile), then upload again, if you want later files to apply as they arrive.
After the Keep-for window on the upload expires, the raw Mode 2 rows are gone. Replay cannot invent Work-Input / Work-Output from events that are no longer visible. Series values that already wrote stay.
Check format (Mode 2 wants event JSON, CSV, or Parquet — not a Mode 1 asset workbook), then mapping (enabled, and it has observed a match), then whether the Asset id in the file matches the Profile id exactly. Silence on the series is unknown coverage, not proof that risk decreased.
Still stuck? Email [email protected] with the Mode (1/2/3), approximate time (UTC), and Asset id — not raw log bodies.