BUG: Issues with Stefan's account

[Comoque1]

Describe the bug It was reported from Stefan that yesterday around 8:30 p.m. NL time, he experienced assigning members to a challenge.

After a brief investigation these are the observations:

1. 2 server pods were restarted at that time

   

2. His account has credential rules but querying storage data related to his profile, fails to be returned:

   
   query {
   user(ID: "83c6da9d-304e-48a2-a9da-5e57e8b80feb") {
   id
   storageAggregator{
     parentEntity{
       id
     }
   }
   authorization{
     credentialRules{
       criterias{
         resourceID
         type
       }
       name
       grantedPrivileges
     }
     privilegeRules{
       grantedPrivileges
     }
   }
   profile {
     displayName
   }
   }
   }

<img width="1329" src="https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBNXdBQkE9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--c0b06c7bee95f641045fdf0406f273761cecadc6/image.png" alt="image.png" />

3. Around 20 minutes before he tried to assign users (assumption based on logs) there were many errors related to save-request which is triggered from WBs
<img width="1858" src="https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBNkFBQkE9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--81bf6d7f7574f6725dc87f318fe23190a6f87a37/image.png" alt="image.png" />

**Expected behavior**
Stefan and any other user can operate on the platform, without experiencing any issue

**Additional context**
Should be consider that Stefan's is using changed email for hist profile.
Stefan was also experiencing this week issued like: not being able to save WB, stop being able to upload visuals, etc.

[techsmyth]

@Comoque1 have you tried resetting authorization on his profile? That userID error is when an exception is thrown and it tries to get the userID but fails. It might already be fixed in develop; it is hiding the original error.

[Comoque1]

@Comoque1 have you tried resetting authorization on his profile? That userID error is when an exception is thrown and it tries to get the userID but fails. It might already be fixed in develop; it is hiding the original error.

Yes, policies of the user were reset.