here is a video of the issue: https://youtu.be/rYNfEz9vg2Y

@seanod are you still seeing this behavior in your page? If so would it be possible to grab a network trace from when the page errors? 

@butlerj many thanks for the response, yes he issue still exists and I've been in touch with Nintex about it - they have recommended that i raise a support request. Also, ive tested the workflow on a separate instance and the same issue exits there. Im attaching the network HAR.

@seanod looking at the network trace it looks like you're getting a 404 when the tenant is making a request to: https://us.nintex.io/designer_/api/connection-defaults/EFSS

Within your settings area can check and see if Default File Storage is enabled or disabled? If it's enabled can you try disabling it and seeing if that resolve the issue? Your workflows should no longer need the Default File Storage as they will all use the out of the box blob storage provided as part of your tenant.

Oh, did i say we have two NWC tenants and I've exported the workflow from one to the other and the behaviour is the same in both.   The original tenant was Asia Pacific and the new one is West US.  Both are complaining about an invalid date format but reading the js, it looks like a known issue?

if (!isValid(originalDate)) {
throw new RangeError('Invalid time value');
} // Convert the date in system timezone to the same date in UTC+00:00 timezone.
// This ensures that when UTC functions will be implemented, locales will be compatible with them.
// See an issue about UTC functions: https://github.com/date-fns/date-fns/issues/376

@seanod yeah that's really odd as I haven't seen any other reports of this from other users. Were you able to get a support ticket opened?

Hi Butlerj, thanks for your follow up on this. I have opened a case, the recent comms was from Thursday last week,  "I have passed your updates to our team, they are looking into the unsupported date format error." I have requested an update just now. #00398847

PS, this is all resolved now with an update that Nintex helpdesk put through for us.