Enhanced Logging for Import Errors of OData Connector
Users encounter an issue when changing connectors for a specific flow. Currently, when an operation result indicates a failure, it is challenging to pinpoint which step within the flow has encountered the issue. As a result, users are compelled to manually review each step to identify the failed ones, causing unnecessary delays and frustration.
AdminJeffery Maynard
(Product Support Consultant, Novacura)
shared this idea
We regret to inform you that this feature request has been declined. After review, our Product team determined that it does not align with our current product roadmap, particularly as Flow Classic is scheduled to reach end of life at the end of this year.
We appreciate your continued feedback and encourage you to keep sharing your ideas and suggestions with us.
-
William Eriksson
commented
When changing the OData Connector in Workflow/Connectors or if you export/import to a new Flow environment, if there is an issue as there usually are when moving from one IFS Cloud version to another. It would be good idea to improve the Operation Log with Workflow name and Machine Step name where an error occur. If its several/big workflows it takes a long time to pinpoint all the issues and fix them.