I am trying to run prefect orion agent in GKE autopilot. I am using the new prefect cloud. The agent appears to be listening but it isn't handling any items in the queue. It appears to do nothing. And since there are no error logs it is impossible to figure out why it is not working. Even locally after logging in and running the agent it creates the work queue but isn't actually doing anything.

Seems like this channel may be a better place than #prefect-community to post this issue with not being able to see task runs in the UI (Prefect 1)? https://prefect-community.slack.com/archives/CL09KU1K7/p1663867045482139

I'm hoping to View Flow Runs by Deployment. (or when I click a Deployment, see a list of past / upcoming flow runs). Is this an outdated way of thinking about these flows? The power of the UI seems limited to me now, only showing a Deployment's config, but I'd also like to view its run history. Anybody have some advice? Related to: https://github.com/PrefectHQ/prefect/issues/5968 and UI Improvements https://github.com/PrefectHQ/prefect/issues/5917

This video on Prefect's youtube mentions that the github credentials block is coming soon. When will this be exactly?

Hi Team, I'm trying to access below prefect URL but unable to do so

I'm getting the access related issue. I had used this URL sometime back and i didn't face any issue but now i'm facing authentication issue

Can someone assist/advise on this

It is possible to run the agent in 2.0 in a python file instead of doing

prefect agent start  --work-queue blabla

I'm trying to pass a list as a parameter in the Prefect 2.3 UI, and I can't seem to get the format right. I want to start the run via UI interface. I've used square and curly brackets... single and double quotes, but I continue to get the same error:

ParameterTypeError('Flow run received invalid parameters:\n - part_list: value is not a valid list')

When starting a flow run via UI, what is the correct format that the UI expects when passing a list as a parameter?

Hello, I am unable to login to prefect 2.0 cloud UI. I am not getting an just getting blank page

I think I have come across what looks like a UI bug. Here are the steps to replicate it. Let’s say I have a deployment with some parameter with value numeric value such as 202005. When I go to the edit page page. That parameter seems to get recognized as a timestamp and is displayed as such. I’ve included screenshots to illustrate.

Hi. I have now tried the Slack notifications a couple of times without success, and therefore ask the community to get some help. I have setup a app in our slack - and the webhook by running the generated curl command to write to a slack channel. and it works fine From what i’ve read, i am supposed to use the same webhook-url in the setting in the prefect URL when i select a notification through Slack. However, nothing happens when a flow fails! and if I instead try to be notified through e-mail it works as expected. Do you have any recommandation on what to do? its’ difficult to troubleshoot the slack notification since they just happens behind the scene..

Hi, I have a suggestion about logs in flows / tasks overview. I usually have a lot of logs and its difficult to scroll down to the most recent ones. Can you do some button which would automagically scroll to the verry bottom of the logs?

Hi guys, does anyone know what am I suppose to put in the Handle section when creating a workspace?

Hi, I have a flow with 4 calls to a data API (thus 4 tasks), which all depend on a get_token task. I call all get_data tasks with .submit(wait_for=[capture_get_token]). The result of this get_token function is cached. When the cache is not yet filled, my radar view looks as it should, with the data tasks on the layer next to the token task. However, when a cached result is used, the radar view looks as in the attached image. Is this as intended? I would expect it to show a dependency nevertheless.

Hi guys, It seems some of my account information was deleted after porting over to the new UI. Not sure how I can get this fixed

as a huge LOTR fan and new prefect user, i was pleasantly surprised to see this random name pop up!

Also - anyone have any idea why I'm getting the following lengthy error when I manually run a flow from the UI? The flow runs fine locally, the agent's running, it's a simple DBT project. I followed the docs exactly. Thoughts?

Flow could not be retrieved from deployment.
Traceback (most recent call last):
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "C:\Users\36350admin\AppData\Local\Temp\2\tmp6kmb0zxkprefect\dbt_flow.py", line 35, in <module>
    run_dbt()
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\flows.py", line 388, in __call__
    return enter_flow_run_engine_from_flow_call(
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\engine.py", line 159, in enter_flow_run_engine_from_flow_call
    return anyio.run(begin_run)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\anyio\_core\_eventloop.py", line 70, in run
    return asynclib.run(func, *args, **backend_options)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\anyio\_backends\_asyncio.py", line 292, in run
    return native_run(wrapper(), debug=debug)
  File "C:\Python\lib\asyncio\runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "C:\Python\lib\asyncio\base_events.py", line 646, in run_until_complete
    return future.result()
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\anyio\_backends\_asyncio.py", line 287, in wrapper
    return await func(*args)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\client\orion.py", line 82, in with_injected_client
    return await fn(*args, **kwargs)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\engine.py", line 232, in create_then_begin_flow_run
    state = await begin_flow_run(
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\engine.py", line 365, in begin_flow_run
    await result_filesystem._save(is_anonymous=True)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\client\orion.py", line 82, in with_injected_client
    return await fn(*args, **kwargs)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\blocks\core.py", line 760, in _save
    await self.register_type_and_schema(client=client)
TypeError: object NoneType can't be used in 'await' expression

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\engine.py", line 257, in retrieve_flow_then_begin_flow_run
    flow = await load_flow_from_flow_run(flow_run, client=client)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\client\orion.py", line 82, in with_injected_client
    return await fn(*args, **kwargs)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\deployments.py", line 70, in load_flow_from_flow_run
    flow = await run_sync_in_worker_thread(import_object, str(import_path))
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\utilities\asyncutils.py", line 57, in run_sync_in_worker_thread
    return await anyio.to_thread.run_sync(call, cancellable=True)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\anyio\to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\anyio\_backends\_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\anyio\_backends\_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\utilities\importtools.py", line 193, in import_object
    module = load_script_as_module(script_path)
  File "C:\Users\36350admin\prefect\venv\lib\site-packages\prefect\utilities\importtools.py", line 156, in load_script_as_module
    raise ScriptError(user_exc=exc, path=path) from exc
prefect.exceptions.ScriptError: Script at 'dbt_flow.py' encountered an exception

I had some minor UI feedback (v2.5.0) found alongside my recent issue #7134: • the time axis uses hh:mm format. The leading 0, for times like 04:22 seems odd for PM times / wastes space. i suggest including PM somewhere if we are zoomed inside the hour boundaries. (it does show 09 PM on the left screenshot, but if you plot 09:01 - 09:59, you won't have that) • Y-axis values of

1h, 1h

is not ideal

Hi folks, on Prefect UI, when a task fails, how can I rerun this task and all the downstream tasks (which also failed, in "TriggerFailed" status). I tried "restart" the task, but realize it only rerun that specific task, not the downstream ones.

Can anyone point me at a support page for Prefect Cloud (1.0) users who can't seem to sign up correctly? I have a collaborator who I've been trying to add for months and the password reset loop is just plain broken. Without an account, the user doesn't have access to a support chat. However, with an account, I also effectively don't have access to support, since it's stuck in "An agent is on the way." perpetually.

Logging into Prefect Cloud 2.0 via MS Edge on MacOS appears to be broken (Chrome is working). Anyone else having this issue? Looks like due to a MIME type issue with one of the script files:

Hi guys - I have recognized the 2FA for logging in. Would it be possible to set this as a setting? Not a big fan of entering a code every time I want to login tbh...

Is there a way to have some sort of a drop-down for the parameter field? Provide a list of options with acceptable parameter values?

Prefect 2's UI seems to show me a mostly-blank page (only the menu & navbar are rendered). https://app.prefect.cloud/ I can check the boxes for 2 workspaces: "benzestyai" and "Zesty AI" (my company), but it doesn't change the blankness of the middle part of the page. I have one coworker (@Timothy Tse) who is setting up Prefect 2 for our organization, and he can see everything fine. Any tips, or ideas for what might be going wrong? I should mention, there was one time where I refreshed https://app.prefect.cloud/, and actually saw a little diagram in the white space, showing presumably flow runs or something rendered as little coloured marks. But then I refreshed again and it went away forever. >_> Edit: cleared my cookies and it worked now. 😂

Hi Guys, we are having a zombie flow run that we cannot kill: When we enter the flow run in UI it's empty - please take a look to the print screens. In the logs we are receiving

[2022-10-18 14:42:58,717] ERROR - xyz| Failed to query for flow run metadata
Oct 18 16:42:58 datalake01 bash[17042]: Traceback (most recent call last):
Oct 18 16:42:58 datalake01 bash[17042]:  File "/usr/local/lib/python3.8/dist-packages/prefect/agent/agent.py", line 331, in _submit_deploy_flow_run_jobs
Oct 18 16:42:58 datalake01 bash[17042]:    flow_runs = self._get_flow_run_metadata(flow_run_ids)
Oct 18 16:42:58 datalake01 bash[17042]:  File "/usr/local/lib/python3.8/dist-packages/prefect/agent/agent.py", line 691, in _get_flow_run_metadata
Oct 18 16:42:58 datalake01 bash[17042]:    result = self.client.graphql(query)
Oct 18 16:42:58 datalake01 bash[17042]:  File "/usr/local/lib/python3.8/dist-packages/prefect/client/client.py", line 570, in graphql
Oct 18 16:42:58 datalake01 bash[17042]:    raise ClientError(result["errors"])
Oct 18 16:42:58 datalake01 bash[17042]: prefect.exceptions.ClientError: [{'path': ['flow_run', 0, 'id'], 'message': 'Cannot return null for non-nullable field flow_run.id.', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]

We tried to restart the agent service and rebuild the docker image but this zoombie is still running. We have the flow run id and when we query it the state is running. Do you have any idea how to kill the flow run? Its Prefect 1. cc @Angelika Tarnawa

When viewing the Flow Runs list in Prefect 2, what are you most interested in seeing about a run, other than the status?

Trying to save a KubernetesJob block and remove the customizations - it fails to store nothing for this field and keeps the old value