Vinay K.

Hi steve.waldron, It is working for us, please try to re-login again and see if it works for you

Standard PostgreSQL connector actions such as Insert, Update, and Upsert are executed and committed individually. Once an operation is committed, Workato does not provide a native rollback option to undo that previously completed action. Maybe you would need to implement compensating actions, such as deleting a previously inserted record if a subsequent operation fails. Let's see if anyone else responds to this with more information

You can use the Run custom SQL action and handle the transaction at the PostgreSQL level using BEGIN, COMMIT, and ROLLBACK, or encapsulate multiple database operations in a stored procedure.

Hi Priyanka B., as far as I have seen, the Workato PostgreSQL connector does not provide transaction handling similar to webMethods Local Transaction or XA Transaction.

it will work, try to create new proper csv and check once again

Hi sonal, Workato does not provide a native Dead Letter Queue (DLQ) like MuleSoft or messaging platforms. To understand the retry and DLQ implementation, we should review the recipe's Handle Errors configuration, connector-level retry settings (if applicable), and the overall error-handling design. We should also verify whether failed payloads are persisted in a Data Table, database, S3, or another storage mechanism for replay, as this typically serves as the application's DLQ. Additionally, reviewing failed job logs in the Jobs section will help identify the current retry behavior and failure handling.