AsyncActionRequest Timestamp in Landmark

Why does my Landmark Transaction query of AsyncActionRequest show 'TimeToExec' as the actual time plus 5 hours? When I view the action in 'My Actions' or the detailed schedule, it displays the correct date and time, including hours. I've been asked to patch a flow that has requirements based on the date and time of the 'TimeToExecute' field. What am I missing, do I have to (re)format the time?

0712131256598360.doc

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

Within the Schedule setup we are using a schedule time zone of Eastern Standard Time. I found the Data Area > Time Zones and we are using Amer/New_York EST which shows the Standard Time Offset Hours of -5, Observes DST and is In Use. I'm guessing that the data is stored using standard time vs EST, but the forms show the time correctly.

russel-cornelson

This is probably better asked in the Landmark Environment Section. Process Automation uses Landmark Environment Async code to handle the scheduling of flows.

But from experience, I can tell you that ALL datetime's stored in Landmark are stored at GMT time; the user interface based on your locale/timezone adjusts and displays the times in your local time zone automatically. But if you are accessing the data through the database, you are going to find GMT times.

If you are modifying the datetime of AsyncActionRequest through the database, you should run this past the Landmark Environment group first or at a bare minimum go through rigorous testing before touching Production.

Copyright © 2025 Infor. All rights reserved.