Override output timestamp when the output is also input for the analysis
If the output of your analysis is also used as an input for the analysis, the option offset the output timestamp relative to the trigger time is grayed out and you see the message "Cannot override output time stamp if any output is used as an input within an analysis". This protection makes sense sometimes because you could cause unsafe triggering scenarios, but there are also valid configurations that are blocked by this. It would be good if there was some way to override this protection in AF in certain situations.
The PI Square post below also describes a similar use case:
For this particular use case, you should be able to use the TagTot() function which executes at 6:00am with an output timestamp override for 5:30am. It’s not clear why you’re using output as input. Can you provide an example?
One example of crazy time stamp shifting would be lab samples. Samples from the day before are tested some time, any time, later in the day or sometimes a few days later with the time stamp forced back to match the sampled time (i.e., using PutVal or DataLogger). The analyses need to wait for the samples to be entered, but then refer to them at the sampled time then apply it's override for final synching of the output.