AWS Scope - "Either put activity inside scope activity or create a valid connection"

Help Studio
1

Has anyone encountered this error using the aws scope to upload files / folders to s3?
Activity was working fine until about two / three weeks ago - now getting validation error: either put the activity inside scope activity or create a valid connection.

The upload activity is inside the aws scope, I know there’s no permission issues because the activity was working fine until recent. Anyone have any insight ?

2 Likes
2

@eestwick

Did you recently had a studio upgrad eor so?

If so try changing the aws package version also and check if the issue persists

Also it would be good idea to check the inner exception details

Cheers

3

Hi @eestwick - did you ever get a resolution to this? Im experiencing the same issue at the moment. I have an open support ticket, but as yet no luck on solving it.

4

Same issue here. I have been experiencing this for at least a month and a half. It happens every time I open any of my projects that use the Amazon Web Services Scope activity. It is incredibly frustrating. I’ll open a project that has previously been saved and even published without any validation errors, and it will immediately give me the yellow validation warning icon on the AWS activity.

An annoying work around I have found is to cut the entire activity and paste it back in. Usually this gets the validation error to go away on the first try, but sometimes I have to try multiple times. Doing this will at least let me work on the project without this validation issue and let me publish any changes I make. Of course I have to perform this exact same workaround if I close the project and reopen it.

As of today, I’m on the latest version of Studio: 2023.4.4 and I am still seeing it. My guess is I’ve been seeing it for at least 2 or 3 recent versions.

5

I spoke to support earlier this week, and this seems to be an issue with the latest few versions of the Amazon package - definitely 2.4 & 2.5. Downgrading the Amazon activities package to v2.2 resolved the issue for me immediately, although I did have to replace most of the activities after the package downgrade.
I’m not sure if v2.3 also has an issue, I havent tested that.

Hope that helps!

6

Confirmed, 2.3 worked.

7

Did anyone have any updates on this? About to downgrade to 2.3.

8

How is this still not fixed in the latest versions?