Sometimes archive entries are lost when changing archive values via the API

• Related Articles

• When the API is used to write archive values with future timestamps, the data cannot be shown with timefilters other than "No timefilter"

  Summary When the API is used to write archive values with future timestamps, the data cannot be shown with timefilters other than "No timefilter". If a specific time filter is set, no data is shown in a trend/report/archive revision screen. ...

• SQL evacuation failure with double entries in archive file

  Summary The SQL evacuation stops if in the archive file are two identical values. Identical means same NameID same Value same Timestamp same Status. These entries could happen if in the archive configuration the option 'save process image during ...

• Manual values for historian is no longer inserted into the correct archive

  Summary Inserting manual values into an archive of the historian, or changing manually changing a value, creates a new archive instead of changing / inserting the value in the correct archive DescriptionInserting manual values into an archive of the ...

• When writing archives fails via API a messagebox is shown instead of return value.

  Summary Messagebox regarding archive writing failure should be suppressed when the saving via the API fails. Instead a return value should be returned by the called function. Description Messagebox regarding archive writing failure should be ...

• Archive with event-triggered recording saves wrong values after runtime was restarted

  Summary @Daniel Kieninger Please verify also: The start image functionality for via function started archives. The values in aggregated archives when the capsule of the basis archive was open via Service Engine end. The first recorded record when ...