Skip to content

Adjusting tiered license levels slow to reflect update #1121

Open

Description

@jorwoods

Describe the bug

When making an adjustment to a tiered license level on a site, trying to add the user for that tier too soon after can fail. Even if the server responds to one query with the correct number, the next query can return the old number. Unclear how long it takes for this setting to propagate.

Versions

Details of your environment, including:

  • Tableau Server version (or note if using Tableau Online) 2022.1.1 (20221.22.0415.1144)
  • Python version 3.8.10
  • TSC library version 0.22

To Reproduce

Steps to reproduce the behavior. Please include a code snippet where possible.

import itertools as it
import time

import tableauserverclient as TSC

# sign in to server as server admin
site = server.sites.get_by_id(server.site_id)
existing_limit = site.tier_creator_capacity
expected_limit = existing_limit + 1

site.tier_creator_capacity = expected_limit
site = server.sites.update(site)

results = [existing_limit] * 3

for i in it.count(1):
    print(f"{i=}; {results=}; {expected_limit=}")
    time.sleep(1)
    site = server.sites.get_by_id(site.id)
    results[i%3] = site.tier_creator_capacity
    if all(r == expected_limit for r in results):
        break

print(f"Got a matching result after {i} attempts.")

Results

What are the results or error messages received? Can end up taking anywhere between 10 seconds and 3 minutes before a consistent response is returned from the API about the tiered license capacity.

NOTE: Be careful not to post user names, passwords, auth tokens or any other private or sensitive information.

Activity

  1. jacalata commented on Oct 7, 2022

    @jacalata
    Contributor

    I'm not sure how long this should take, but we should find out and add it to the docs.

  2. jorwoods commented on Oct 9, 2022

    @jorwoods
    ContributorAuthor

    The curious part is: hypothetically say you're trying to update the number from 10 to 11. The response will seem to randomly return either 10 or 11 for some amount of time before it consistently reflects the updated number. This behavior also happens in the Web UI, but is easier to reproduce via REST (as well as being where I first noticed the issue).

  3. github-actions commented on Aug 18, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions