DateTimeStart() giving multiple values with AMP

[OllieClarke]

I noticed today that DateTimeStart() can give multiple values if the AMP engine is on

I've got workflows which use the datetimestart() function all based on the assumption that it will only return 1 value (as the documentation implies: ) 

When AMP is off then I get the expected 1 value. 

Is this expected behaviour? And is there a better way of dealing with it than creating a single datetimestart() at the very beginning of the workflow and appending that where needed? Even with this approach, can we trust that it will return the correct value?

Cheers, 

Ollie

[nbondarchuk]

Could you please share the version of Designer where it happened? I wasn’t able to reproduce it with the latest one.

[OllieClarke]

Hi @nbondarchuk,

version 2022.3.1.395  I think it might be dependent on data size, so if you up the number of records generated that might swing it for you

[nbondarchuk · Accepted solution]

Thank you for reporting an issue and for the workflow attachment. I was able to reproduce it too once I changed number of running threads. 

We will create a defect to fix it. The same behaviour you can see with the Original Engine as well when using same function several times in the workflow.

[nbondarchuk · Accepted solution]

I’m happy to announce that the issue has been fixed in the 2023.1 GA Release version, which is available for download from our licensing portal. 

[OllieClarke]

@nbondarchuk 👏👏👏

[KleistNils]

The problem is still there in Version: 2023.2.1.89 Patch: 2