Using the replay plugin with datastore mapping of specific log entries works as intended when the desired log entry is present from the beginning.
However, if the entry exists in the log but has no value in the beginning, for example when it comes from a task added during control, the creation of the datastore entry throws.
This occurs here at the allocation of the datastore entry.
Maybe there is a better way to do this using some functions of the replay plugin, but I thought the expected behavior would be to output zero while the entry does not exist and the log value when it exists in the replay.
Using the replay plugin with datastore mapping of specific log entries works as intended when the desired log entry is present from the beginning.
However, if the entry exists in the log but has no value in the beginning, for example when it comes from a task added during control, the creation of the datastore entry throws. This occurs here at the allocation of the datastore entry.
Maybe there is a better way to do this using some functions of the replay plugin, but I thought the expected behavior would be to output zero while the entry does not exist and the log value when it exists in the replay.