Subscription inconsistently displaying between Active and Inactive #87198
Labels
No Label
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Content
Type
Design
Type
Report
Type
To Do
Type
Web Development
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio#87198
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I recently purchased a subscription to Blender Cloud, and when I am logged in, I can access the Libraries of Characters and other assets, and my profile icon will display that my subscription is Active, as it should. However, I am NOT able to access anything in the Training services. Furthermore: When I am on the Training section of the website, my profile icon will suddenly be Red, and display that my subscription is INACTIVE.
This is very confusing. I would understand if my subscription simply did not allow access to the Training services specifically, but it still seems very strange that my entire account status suddenly becomes "INACTIVE" when I am on that page. As a consequence, I also cannot view any information detailing my subscription. When I click on "Subscription" for my profile, it simply displays that I do not have a subscription active at all, which is incorrect.
Added subscriber: @Byakkojin
Added subscriber: @railla
Changed status from 'Needs Triage' to: 'Resolved'
@Byakkojin There was a problem with the trainings section of the Cloud: new subscription statuses failed to propagate correctly which is why your account was displayed as inactive.
This problem has been fixed and you should be able to see all of the Cloud's content now.
Thank you for reporting this issue and apologies for the confusion!