i

    itay livni

    2 years ago
    Hi - I am trying to understand the error message from flow.register. Is the message indicating that the flow is not valid?
    prefect.utilities.exceptions.ClientError: [{'path': ['create_flow_from_compressed_string'], 'message': '[{\'extensions\': {\'path\': \'$.variableValues\', \'code\': \'validation-failed\'}, \'message\': "no such type exists in the schema: \'flow_group_insert_input\'"}]', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]
    Thanks
    j

    josh

    2 years ago
    Hey @itay livni this looks to be an authorization issue with Cloud. What token type are you using? e.g. on your machine (where you are running register) did you perform a
    prefect auth login -t
    with a USER token?
    i

    itay livni

    2 years ago
    @josh I tried
    prefect auth login --token xyz
    and was getting
    Auth token already present in config.
    j

    josh

    2 years ago
    Do you have a token set in your
    ~/.prefect/config.toml
    ? I believe error message means you have a manual override and it shouldn’t be needed
    i

    itay livni

    2 years ago
    Yes I do
    j

    josh

    2 years ago
    Comment that out and then try login again with a USER token
    i

    itay livni

    2 years ago
    Ok this is what I did incorporating your suggestion.1. Created a new PAT (Personal Access Token) 2. Logged in successfully using
    prefect auth login -t new-token
    3. registered successfully. when I retried uncommented auth in config.toml it register failed again
    j

    josh

    2 years ago
    Yeah the token in your config probably is not a PAT so it does not allow registration
    You don’t need to have a token in the config.toml, when you login the PAT is persisted on disk
    i

    itay livni

    2 years ago
    Totally confused. Up to 12.1 I had some token (maybe runner) stored in the config. And I could register with no problem. Now with same token saved in config,toml for cloud secrets ect ... It needs to be removed?
    j

    josh

    2 years ago
    Let me check, I don’t think anything auth related has changed recently and IMO I’m not sure how you were able to register with a RUNNER token before
    Okay I have some clarification. Now that flow registration touches flow groups RUNNER tokens (which should be used for agents / flow runs) can’t perform the registration because they do not have permissions to create flow groups.
    i

    itay livni

    2 years ago
    Thank you for the clarification 👏