When data profiling job(backend job) is failed with an unhandled exception, the job does an inordinate number of retries causing additional cost to the customer.

This issue occurs if the Amorphic deployed with single tenancy and have datasets with data profiling enabled.

Affected Versions: 1.11, 1.12, 1.13, 1.14, 2.0, 2.1

Fix Version: 2.2

Workflows sending incorrect notifications in scenarios mentioned below(Only when user is subscribed to workflow alerts)

• when we have non-etl nodes in the workflow, even after the successful execution of the workflow system sends incorrect node failure email alert.
• when the any node in the workflow failed, push notification shows error message and details but the status in the push notification says success.

Sample incorrect email notification details:

Title: Workflow 'abcd' encountered one or more node failures.

EventType: Node Execution Failure

ErrorMessage: Job run succeeded

Affected Versions: 2.1 2.0 1.14 1.13

Fix Version: 2.2

Data ingestion using the connections(JDBC bulk-load type) is failing because bulk-load task & instance creation are failing with empty sequence error. AWS boto3 method describe_orderable_replication_instances was started sending more number of instances with pagination, amorphic was not equipped to handle the pagination which resulted to send the empty list of instances in Amoprhic API response.

Affected Versions: 2.0 1.14 1.13

Fix Version: 2.1 2.0* 1.14* 1.13*

Resource sync process for Redshift datasets are failing with error (RTE-1001, 'adp'.) in a non multi-tenant environment where the tenant table is empty and the dataset or the domain table records do not have TenantName metadata in them. When the TenantName metadata is added to the records in datasets and domain table, the process is sending incorrect emails with message "Dataset which was created using Amorphic was deleted via AWS console" for all redshift datasets.

Affected Versions: 2.0

Fix Version: 2.1 2.0*

User is Failed to create/update connection of type JDBC(SQL Server only) becuase of the updated driver version.

Affected Versions: 2.0

Fix Version: 2.1 2.0*

Users are losing access to redshift tables and views after running user repair or by generating access parity report

Affected Versions: 2.0 1.14

Fix Version: 2.0* 2.1