Skip to content
← Novacura Flow Classic

How can we improve Novacura Flow?

Novacura Flow Classic: Connectors

Categories

(thinking…)

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.

8 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

AdminJeffery Maynard (Product Support Consultant, Novacura) shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
under review  ·  AdminIrshad Hassan (Admin, Novacura) responded  · 

Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • William Eriksson commented  ·   ·  Report

    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.