Hello, I am trying to setup a prefect agent into AWS ECS task... it worked, but inside the python scripts this prefect agent is running, I am instancing a boto3 to talk to our SSM Parameters but I am getting an "AccessDenied" Error. It must be related to policies, but I have a hard time solving that issue (editing policies, editing roles... etc and still getting the same thing)

botocore.exceptions.ClientError: An error occurred (AccessDeniedException) when calling the GetParameter operation: User: arn:aws:sts::999999999999:assumed-role/MyRole-dev/12345459ba45458183ed3d1aa5112341 is not authorized to perform: ssm:GetParameter on resource: arn:aws:ssm:region:999999999999:parameter/XXX/value because no identity-based policy allows the ssm:GetParameter action

What is your suggestion here, or a possible solution for this?

How do I tell Prefect to run exactly one copy of a Flow, starting immediately, until the Flow ends (variable amount of time), then immediately start another single copy, and so forth? ... by "copy" I just mean I wouldn't want the Flow runs to overlap

Is it possible to run a task B on a schedule, but also iterate through a list returned from an upstream task A? So for each rerun of given task B, it will iterate through the list from task A one iterable at a time

hey guys. trying to set the local configuration path, but is not being found. I’m doing as docs `export PREFECT__USER_CONFIG_PATH="path/to/config.toml"`I tried using both an absolute and a relative path and nothing. also tried settings the config (Slack webhook url) directly into the code, like this discussion and nothing, still getting the same

ValueError

where it can’t find Slack webhook URL

@Marvin I keep getting this error: TypeError: ‘type’ object is not iterable My prefect version is v2.20.2 pydantic Version: 2.8.2 typer Version: 0.12.4 what is causing this?

@Marvin Prefect 3.x How can I run a deployed flow as a subflow so I can get the returned data from the workflow to pass to another function?

@Marvin How do I re-continue a crashed flow from where it crashed?

I’m running a flow where both the flow and the tasks have retries. For the first run the task with retries behaved as expected waiting retry_delay_seconds between each attempt. Then after the number of retries was exhausted the flow retry kicked in and waited retry_delay_seconds before trying the flow again. So far so good. The issue I have is that on the second flow attempt the task did retry three times, but didn’t respect the retry_delay_seconds and just ran the three tries one after the other really fast. Is this expected behaviour or did I land on a bug?

We have a few tasks that are hanging and taking the concurrency limit, but their flow has been cancelled. How do we cancel those tasks?

I have a prefect flow which consumes messages from rabbitmq, I want this task to run continuously, what would the schedule be? I am thinking of starting the flow and then include max_retries and retry_delay for the task which consumes from rabbitmq, is there a better way? thank you