Hi Sharvari. Weâre checking on the UTC time issue. Can you please elaborate on what other issues you are seeing? Why are the string operations necessary? This will help me understand the exact issue and communicate to the workflows team.
Based on current documentation and suggestion in workflow, I spent a lot of time trying to make the step work with MM-DD-YYYY format. Once I found out it uses ISO8601, I had to use the string operations to come up with midnight date for managing identities. I used the substring and string concatenation to get a date in the correct format. Ex. 2024-11-19T05:00:00.000Z
This isnât an ideal solution and this works for now but there would be an issue to adjust this value during DST start/end. It would be nice to have a flag for DST on/off for this setting.
The issues with Wait Until step -
Date format usage not clear MM/DD/YYYY v/s ISO8601.
If picking dates from UI it shows MM/DD/YYYY format but when providing via variables it expects a different format(ISO8601).
If weâre using a variable to set date, the same variable has to be provided in both date and time fields and it should be a date timestamp like the example above. If we provide only the date part eg. 2024-11-19 in date and select 12:00 AM in Time drop down or provide 12:00 AM in a separate variable and pick a date, it doesnât work. The step works only if both fields reference the exact same date timestamp in ISO8601 format. This was also not clearly documented. Technically if this is the case, there should be only one date/time field instead of two while using Wait Until.
I would like to suggest adding a DST field which can be set to on/off to adjust the timestamp accordingly.
I spoke with @tburt and he agreed that the documentation can be more clear on what inputs are expected in this action. The docs team will be updating that. As for the DST request, can you please submit an idea?
I am also running into similar issues with wait action workflow. Even though I used a transform to convert the date output in âISO8601â date format, the wait until action is throwing error.
Example output format: 2025-01-13T00:00:00.000Z
My date input in the wait action is in ISO8601 format. Is there anything else that is needed to be configured here?
Hi Sharvani,
I am trying to understand this better. My workflow needs to trigger on the date attribute and then it needs to wait until 5 pm est to complete the workflow.
Example:
We would only get date attribute from the source. Using wait action in workflow, it would execute at 5 pm specified in the wait until field
Does the wait until field in the wait action flow not work?
Iâve tried the same time, but there is a limitation wherein if you provide a variable in date and a static time in the Time field, it doesnât take it.
For this scenario to work, append 5 pm EST to your date attribute in a define variable step and then provide that variable in both the Date and Time fields in the Wait step.
Note - In future you will have to address the define variable step for DST timezone changes else your workflow will execute an hour off the expected time.
When can we expect the documentation, the GUI and the execution behaviour to align with each other?
e.g. If we implement the workaround as Sharvari mentioned (thanks for the heads up), then that workflow may break in the future when this is âfixedâ by SailPoint, where we then need to re-adjust the workflow. This is a bit of a tech debt to monitor / circle back on when the fix will be in place.
another vote