5 results found
-
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.
7 votesThank 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.
-
Additional Authentication Options for Email Connector
Microsoft is discontinuing basic HTTP authentication for Exchange on October 1st. While SMTP basic authentication, which appears to be used in our email connectors, will continue to function based on Microsoft's documentation:
Deprecation of Basic Authentication in Exchange Online
Considering this deprecation, Microsoft advises us to explore alternative options. Anticipating that similar queries may arise from various customers, we kindly request the development of a new email connector (or an update to the existing one) that supports alternative authentication protocols. This proactive approach will help address potential customer demands as they begin to inquire about this change more frequently.
6 votesThank 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.
-
The possibility to handle errors in some connectors
In some connectors for example FileSystem we need the ability to handle errors and sometimes ignore them.
5 votesThank 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.
-
OData Connector Attribute List Ordered Alphabetically
We would like “Order of attributes“ is an example where attributes have no order to be ordered alphabetically. In Read operation keys (indicated bold already at the moment) could be first in the list and the remainder of the list should be ordered alphabetically.
3 votesThank 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.
-
Add timeout error Handling for REST APIs
Currently, while flow 6 connectors handle REST-API errors based on status codes, they fall short in handling timeouts. A feature that handles timeouts would greatly improve our application's error management.
1 voteThank 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.
- Don't see your idea?