starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #3381] [bug]: Workspaces/Team Environments get's deleted by changing Team #1129

New issue

Closed

opened 2026-03-16 18:47:45 +03:00 by kerem · 7 comments

kerem commented

2026-03-16 18:47:45 +03:00

Owner

Originally created by @RaHehl on GitHub (Sep 21, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3381

Is there an existing issue for this?

I have searched the existing issues

Current behavior

Team environment get's deleted if u switch the team

Steps to reproduce

I create a environment with var's for a Team, it get's send to the server via graphql
I select another team
i select the prior team
my environments are gone

Environment

Production

Version

Self-hosted

Originally created by @RaHehl on GitHub (Sep 21, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3381 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior Team environment get's deleted if u switch the team ### Steps to reproduce - I create a environment with var's for a Team, it get's send to the server via graphql - I select another team - i select the prior team - my environments are gone ### Environment Production ### Version Self-hosted

kerem

2026-03-16 18:47:45 +03:00

closed this issue
added the
bug

need testing

self-host
labels

kerem commented

2026-03-16 18:48:01 +03:00

Author

Owner

@RaHehl commented on GitHub (Sep 21, 2023):

it's a little strange. I created the bug based on repeated feedback from multiple internal users. After I was able to reproduce the behavior even in incognito mode. env created team changed, everything empty. Now suddenly all the previously disappeared env are back and I can no longer reproduce it.

@RaHehl commented on GitHub (Sep 21, 2023): it's a little strange. I created the bug based on repeated feedback from multiple internal users. After I was able to reproduce the behavior even in incognito mode. env created team changed, everything empty. Now suddenly all the previously disappeared env are back and I can no longer reproduce it.

kerem commented

2026-03-16 18:48:06 +03:00

Author

Owner

@balub commented on GitHub (Sep 25, 2023):

Hey, @RaHehl I want to confirm the issue so we can narrow down and find the problem.

The issue is basically when you create environment variables for a given team say "Team A" and you switch to another team say "Team B" with no environments in it. Now when switching back to Team A the environments are all missing.
Is this is issue or am I missing anything?

@balub commented on GitHub (Sep 25, 2023): Hey, @RaHehl I want to confirm the issue so we can narrow down and find the problem. - The issue is basically when you create environment variables for a given team say "Team A" and you switch to another team say "Team B" with no environments in it. Now when switching back to Team A the environments are all missing. Is this is issue or am I missing anything?

kerem commented

2026-03-16 18:48:11 +03:00

Author

Owner

@RaHehl commented on GitHub (Sep 27, 2023):

@balub Right, that was the behavior I had, but now I can't reproduce it.

But I just noticed something: maybe it has something to do with bug #3393. I originally attached a screenshot of the request here, but when I saw that a CreateUserEnvironment was visible in the image instead of a CreateTeamEnvironment, I took the screenshot out again because I thought I had included it incorrectly.

In addition, I just had the behavior that I was logged in from yesterday (via MS), but I couldn't see my teams until I logged out and logged in again. Other users have sporadically reported the same behavior to me in our instance.

@RaHehl commented on GitHub (Sep 27, 2023): @balub Right, that was the behavior I had, but now I can't reproduce it. But I just noticed something: maybe it has something to do with bug #3393. I originally attached a screenshot of the request here, but when I saw that a CreateUserEnvironment was visible in the image instead of a CreateTeamEnvironment, I took the screenshot out again because I thought I had included it incorrectly. In addition, I just had the behavior that I was logged in from yesterday (via MS), but I couldn't see my teams until I logged out and logged in again. Other users have sporadically reported the same behavior to me in our instance.

kerem commented

2026-03-16 18:48:16 +03:00

Author

Owner

@RaHehl commented on GitHub (Nov 1, 2023):

A user saw something like this in the dev tools when it occurred:
operationName: GetTeamEnvironments
Throttling 419

Is it Possible this "throttler-behind-proxy" https://github.com/hoppscotch/hoppscotch/blob/main/packages/hoppscotch-backend/src/guards/throttler-behind-proxy.guard.ts

Is not configured for the "team-environments.resolver"
https://github.com/hoppscotch/hoppscotch/blob/main/packages/hoppscotch-backend/src/team-environments/team-environments.resolver.ts

With the result: The requests of all users via the Kubernetes Ingress Proxy are counted as coming from one IP, the IP of the Ingress Proxy?

@RaHehl commented on GitHub (Nov 1, 2023): A user saw something like this in the dev tools when it occurred: operationName: GetTeamEnvironments Throttling 419 Is it Possible this "throttler-behind-proxy" https://github.com/hoppscotch/hoppscotch/blob/main/packages/hoppscotch-backend/src/guards/throttler-behind-proxy.guard.ts Is not configured for the "team-environments.resolver" https://github.com/hoppscotch/hoppscotch/blob/main/packages/hoppscotch-backend/src/team-environments/team-environments.resolver.ts With the result: The requests of all users via the Kubernetes Ingress Proxy are counted as coming from one IP, the IP of the Ingress Proxy?

kerem commented

2026-03-16 18:48:21 +03:00

Author

Owner

@balub commented on GitHub (Jan 11, 2024):

@RaHehl I apologise for the time it took to get to this issue, but after looking into this it seems certain field-resolvers for certain modules do not have any rate-limiting on them. In addition to that maybe the lack of extracting the source IP of the requests in the GqlThrottlerGuard could cause issues when working with proxies. Will run some tests to confirm the same.

@balub commented on GitHub (Jan 11, 2024): @RaHehl I apologise for the time it took to get to this issue, but after looking into this it seems certain field-resolvers for certain modules do not have any rate-limiting on them. In addition to that maybe the lack of extracting the source IP of the requests in the `GqlThrottlerGuard` could cause issues when working with proxies. Will run some tests to confirm the same.

kerem commented

2026-03-16 18:48:26 +03:00

Author

Owner

@balub commented on GitHub (Jul 17, 2024):

@RaHehl are you still encountering this issue, if not I believe its safe to close this issue ?

@balub commented on GitHub (Jul 17, 2024): @RaHehl are you still encountering this issue, if not I believe its safe to close this issue ?

kerem commented

2026-03-16 18:48:31 +03:00

Author

Owner

@RaHehl commented on GitHub (Jul 17, 2024):

@balub At least I haven't had any reports from users about this for a while, so I agree with you closing this

@RaHehl commented on GitHub (Jul 17, 2024): @balub At least I haven't had any reports from users about this for a while, so I agree with you closing this