4 results found
-
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.
-
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.
2 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.
-
Telemetry on Concurrent Sessions
As a developer or admin of an organization, I would like to see how many concurrent sessions are being utilized in a given period on each agent to determine if I need to add more agents to an agent group for better performance.
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.
-
More Agent Traceability
As a customer, it would be nice to see exactly what APIs are called on the Agent logs. Currently, we can only see the APIs outbound and inbound in the Diagnostic mode client. But we would like to be able to see all the APIs including payloads and responses inside the Agent Logs for traceability.
The amount of days logged should be configurable and searchable.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?