# Errors after upgrading aws source plugin to v24.1.0 from v22.19.2 **URL:** \ **Category:** CloudQuery Plugins\ **Created:** [February 8, 2024, 8:54pm UTC](https://community.cloudquery.io/t/errors-after-upgrading-aws-source-plugin-to-v24-1-0-from-v22-19-2/388 "2024-02-08T20:54:39Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![comic-firefly](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@comic-firefly](https://community.cloudquery.io/u/comic-firefly)\ **Post date:** [February 8, 2024, 8:54pm UTC](https://community.cloudquery.io/t/errors-after-upgrading-aws-source-plugin-to-v24-1-0-from-v22-19-2/388/1 "2024-02-08T20:54:39Z")
Since upgrading the AWS source plugin to “v24.1.0” from “v22.19.2”, I’m getting errors such as (see in thread): ```auto Failed to drop NOT NULL constraint error="ERROR: column \"request_account_id\" of relation \"aws_directconnect_gateways\" does not exist (SQLSTATE 42703)" column=request_account_id module=pg-dest table=aws_directconnect_gateways 2024-02-08T20:18:24Z INF finished call grpc.code=Canceled grpc.component=server grpc.error="rpc error: code = Canceled desc = plugin returned error: ERROR: column \"request_account_id\" of relation \"aws_directconnect_gateways\" does not exist (SQLSTATE 42703)" grpc.method=Write grpc.method_type=client_stream grpc.service=cloudquery.plugin.v3.Plugin grpc.start_time=2024-02-08T20:18:15Z grpc.time_ms=9691.511 module=cli peer.address=@ protocol=grpc ``` Did I update too aggressively? ---
**Author:** ![ben](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/ben/32/88_2.png) [@ben](https://community.cloudquery.io/u/ben)\ **Post date:** [February 8, 2024, 9:20pm UTC](https://community.cloudquery.io/t/errors-after-upgrading-aws-source-plugin-to-v24-1-0-from-v22-19-2/388/2 "2024-02-08T21:20:38Z")
What version of Postgres are you using? ---
**Author:** ![comic-firefly](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@comic-firefly](https://community.cloudquery.io/u/comic-firefly)\ **Post date:** [February 8, 2024, 9:31pm UTC](https://community.cloudquery.io/t/errors-after-upgrading-aws-source-plugin-to-v24-1-0-from-v22-19-2/388/3 "2024-02-08T21:31:15Z")
Plugin? Version: `v7.3.1` I may have to delete everything and resync. ---
**Author:** ![ben](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/ben/32/88_2.png) [@ben](https://community.cloudquery.io/u/ben)\ **Post date:** [February 8, 2024, 9:32pm UTC](https://community.cloudquery.io/t/errors-after-upgrading-aws-source-plugin-to-v24-1-0-from-v22-19-2/388/4 "2024-02-08T21:32:00Z")
You can use `migrate_mode: forced` ---
**Author:** ![comic-firefly](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@comic-firefly](https://community.cloudquery.io/u/comic-firefly)\ **Post date:** [February 8, 2024, 9:32pm UTC](https://community.cloudquery.io/t/errors-after-upgrading-aws-source-plugin-to-v24-1-0-from-v22-19-2/388/5 "2024-02-08T21:32:11Z")
so I had that initially ---
**Author:** ![ben](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/ben/32/88_2.png) [@ben](https://community.cloudquery.io/u/ben)\ **Post date:** [February 8, 2024, 9:32pm UTC](https://community.cloudquery.io/t/errors-after-upgrading-aws-source-plugin-to-v24-1-0-from-v22-19-2/388/6 "2024-02-08T21:32:20Z")
And that would handle dropping and recreating. Interesting… Ok! I am able to replicate it… ---
**Author:** ![comic-firefly](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@comic-firefly](https://community.cloudquery.io/u/comic-firefly)\ **Post date:** [February 8, 2024, 9:40pm UTC](https://community.cloudquery.io/t/errors-after-upgrading-aws-source-plugin-to-v24-1-0-from-v22-19-2/388/7 "2024-02-08T21:40:02Z")
Alright, I’ll be out for a bit. I asked this in here to not continue to DM you because I get that. I’ll try any suggestions when I get back or wait for a fix. @ben everything is working now. Thank you for all the work you’ve done to get this working for us. Also, I’ve talked to my team about setting up a meeting with your guys, so that will probably happen before we go fully GA with our service.