Hi Steve Klett, I just wanted to let you know that I've seen your feedback about the Product portal, and that we take it seriously. You're also not the only one with these concerns about the portal...
RESOLVED All errors have now been restored for all accounts.
UPDATE The error recovery process has been completed for the majority of accounts. If your account still has errors that have not been restored, you can expect them to be restored over the next few...
UPDATE During the dry run of the restoration process, the team encountered an issue, which has been resolved. As a precaution we have postponed the restoration process 24h, and hence it will instea...
UPDATE We are planning to kick off a process to restore all errors today at 9 pm PST/6 am CET/10.30 am IST tomorrow. You may experience a slight delay in viewing new errors while this process is ru...
UPDATE The team is working hard to fix this issue as soon as possible, and will continue to work over the weekend so that we can release a fix on Monday or Tuesday. We will continue to post updates...
Hi David Gollom and Philippe Foisy, It is not your imagination :) - We cache the preview data until there's a change in the upstream exports. If there has been no change upstream, then the input to...
Glad to hear that this is useful to you David Gollom, we appreciate the feedback! This was implemented thanks to an insight provided by Steve Boot, thank you Steve for bringing this to our attentio...
Hi Bas van Ditzhuijzen We refresh the input data when a change has been made in the flow that impacts the input data. For example, if you are viewing the scipts/hooks editor on a lookup, and you pr...
Thank you Steve Klett, that makes me very happy to hear!