• t

    Thomas Pedersen

    5 months ago
    Normally our flows run successfully, without any problems. However, we encountered this error for two flow runs:
    Failed to set task state with error: ClientError([{'message': 'Unable to complete operation. An internal API error occurred.', 'locations': [{'line': 2, 'column': 5}], 'path': ['set_task_run_states'], 'extensions': {'code': 'INTERNAL_SERVER_ERROR', 'exception': {'message': 'Unable to complete operation. An internal API error occurred.'}}}])
    Traceback (most recent call last):
      File "/usr/local/lib/python3.9/site-packages/prefect/engine/cloud/task_runner.py", line 91, in call_runner_target_handlers
        state = self.client.set_task_run_state(
      File "/usr/local/lib/python3.9/site-packages/prefect/client/client.py", line 1598, in set_task_run_state
        result = self.graphql(
      File "/usr/local/lib/python3.9/site-packages/prefect/client/client.py", line 473, in graphql
        raise ClientError(result["errors"])
    prefect.exceptions.ClientError: [{'message': 'Unable to complete operation. An internal API error occurred.', 'locations': [{'line': 2, 'column': 5}], 'path': ['set_task_run_states'], 'extensions': {'code': 'INTERNAL_SERVER_ERROR', 'exception': {'message': 'Unable to complete operation. An internal API error occurred.'}}}]
    In the same timespan, we had 5 flows running, 3 succeeded, only the 2 failed with the above error. The flows run every hour, in the previous hour and next hour everything was running fine.
    start_time                          end_time                            state   state_message
    2022-04-08T02:00:13.555177+00:00	2022-04-08T02:14:19.782245+00:00	Failed	Some reference tasks failed.
    2022-04-08T02:00:13.558573+00:00	2022-04-08T02:14:23.027744+00:00	Success	All reference tasks succeeded.
    2022-04-08T02:00:13.849767+00:00	2022-04-08T02:14:25.492537+00:00	Success	All reference tasks succeeded.
    2022-04-08T02:00:13.929466+00:00	2022-04-08T02:14:23.787185+00:00	Failed	Some reference tasks failed.
    2022-04-08T02:00:14.427653+00:00	2022-04-08T02:21:56.436942+00:00	Success	All reference tasks succeeded.
    t
    Anna Geller
    4 replies
    Copy to Clipboard
  • Yana Burlaka

    Yana Burlaka

    5 months ago
    Hello, team Prefect! I wonder if there is a way to use SSO in Prefect Server? And to be more precise I’m interested in Okta as SSO provider. Or this feature is only available in Prefect Cloud Enterprise? Thank you
    Yana Burlaka
    Kevin Kho
    8 replies
    Copy to Clipboard
  • Christian Nuss

    Christian Nuss

    5 months ago
    heyo! i'm using
    prefect agent docker start
    ... is there a way to prevent the container from being removed once its completed?
    Christian Nuss
    Kevin Kho
    +1
    34 replies
    Copy to Clipboard
  • Diego Alonso Roque Montoya

    Diego Alonso Roque Montoya

    5 months ago
    Is there a way to clear the data of Prefect?
    Diego Alonso Roque Montoya
    Kevin Kho
    7 replies
    Copy to Clipboard
  • Mariusz Olszewski

    Mariusz Olszewski

    5 months ago
    Is there aby change in security aspects on open source 2.0?
    Mariusz Olszewski
    Anna Geller
    +1
    4 replies
    Copy to Clipboard
  • a

    Alex F

    5 months ago
    Hello Prefect Team , I have a question about Shell Task. During PowerShell execution I am doing gzip operation that works then I run this process in shell manually, without any errors. However during Prefect Shell Task execution it's erroring out. with message "archive entry was compressed using an unsupported compression" . I have a feeling Shell Task spinning up empty bash shell and it's not looking into PowerShell libraries installed for same user as the agent is running under during execution. Any idea how to point Shell Task to same user agent Is running under , or how to tell Shell Task path to Powershell dlls ?
    a
    Kevin Kho
    8 replies
    Copy to Clipboard
  • n

    Niels Prins

    5 months ago
    Hi, Kind a weird question. I'm upgrading from 0.15.3 to 1.2.0 in our k8s environment. When registering a flow as I was used to do (via
    flow.register('test')
    ) the system gives met a
    405 Client Error: Method Not Allowed
    I'm notecing that when I'm using client.graphql(...) I get the same error, unless I point the client to the graphql endpoint. Now my question(s):1. Can I get out of the system why it is giving me a 405? 2. Do I need to register a flow at the UI endpoint or at the GRAPHQL endpoint? we used to do the first in 0.15.3 Hope someone can help chrs Niels Nevermind, FIXED it myself. Just for reference for others. You need the graphql endpoint =D
    n
    1 replies
    Copy to Clipboard
  • Shuchita Tripathi

    Shuchita Tripathi

    5 months ago
    I have installed prefect orion in a VM. do i need any flag similar to --expose to start the server to see the dashboard? --expose is not working. and in vm, the server has started but I can't access it from the browser. in the security group, i have 4200, 4201, 8080 and few other ports open, as I did with prefect 1.0
    Shuchita Tripathi
    Kevin Kho
    +1
    10 replies
    Copy to Clipboard
  • s

    Sam Werbalowsky

    5 months ago
    Hi, I have Prefect Deployed via Helm/Kubernetes, version
    0.15.10
    . Will I run in to issues if I am using a later version
    1.2.0
    of Prefect in the image for the agent/dask worker pods?
    s
    Kevin Kho
    2 replies
    Copy to Clipboard
  • Daniel Ross

    Daniel Ross

    5 months ago
    Hi Prefect Community! I have encountered an issue where when I run a 'flow of flows' the parent flow fails with the following error:
    Error during execution of task: ValueError('You have not set an API key for authentication.')
    This only happens when I use the DaskExecutor. (Notably the child flows succeed.) However, if I specify a LocalExecutor everything is fine. I assumed that the container where the flow is being executed was not able to reach the server, but I can see the PREFECT__CLOUD__API set properly (to the GraphQL port on the Prefect Server) in the ECS task, and the PREFECT__BACKEND is set to "server". Any ideas on what could be causing this problem?
    Daniel Ross
    Anna Geller
    2 replies
    Copy to Clipboard