@Marvin I have two nested tasks: the first task is the second one in a loop so it will be executed many times. Sometimes the second task might fail so I added a

retries=3

in the task decorator. I noticed that the first task appeared twice in the logs which is not expected.

In Prefect 3.x, when a task is retried, a new task run is not created. Instead, a new state is added to the state history of the original task run. This means that the task does not actually execute again as a separate entity, but its state changes to reflect each retry attempt. This behavior should not cause the first task to appear twice unless there's a specific issue in the implementation or logging configuration. Here's a link to the relevant documentation: Prefect Task Retries If the first task is appearing twice in the logs, it might be due to how the logging is configured or how the tasks are structured within the flow. You might want to check if the first task is being called or logged in a way that causes it to appear multiple times. For further assistance, please ensure your task and flow structure are correctly set up, and consider reviewing the logging configuration. If the issue persists, examining the specific implementation might be necessary.

@Marvin My flow seems to run multiple times for no reason. I see in the log a function that is called at the beginning of the flow and I can see it twice in the logs.

The issue of flows running multiple times can be attributed to several factors based on Prefect's behavior and known issues: 1. Duplicate Flow Runs: There have been reports of duplicate flow runs occurring due to scheduling issues, particularly when redeploying frequently-scheduled deployments or during Daylight Saving Time transitions. These issues can lead to unexpected duplicate runs being scheduled or executed. 2. Logging and State Management: Prefect logs might show repeated entries if the flow's state transitions are logged multiple times or if the flow is inadvertently retried or rescheduled. To address this, consider the following steps: - Review Deployment Configuration: Ensure that your deployment schedules are set correctly and that redeployment processes do not inadvertently create duplicate schedules. - Check for Known Issues: Review ongoing issues on Prefect's GitHub repository related to duplicate flow runs. For instance, issue #17538 and issue #8880 discuss scenarios where duplicate runs might occur. - Logging Configuration: Verify that your logging setup is not duplicating entries due to how it captures state changes or retries. For more detailed analysis, examining your specific setup and logs might be necessary. If the problem persists, consider reaching out to the Prefect community or support for further assistance.

@Marvin My flow is running twice within the same run. In Prefect Cloud UI there is the the Run count = 2/1. This is not making any sense.

The "Run count = 2/1" indication in Prefect Cloud UI suggests that the flow has been executed more than once within the same run context. This can occur if the flow encounters a situation that causes it to rerun, such as a failure or a retry condition that triggers the entire flow to execute again. Here are some possible reasons and steps to consider: 1. Rerun Trigger: The flow might be configured to rerun under certain conditions, such as task failures or specific retry settings. Check if there's any logic or configuration that might be causing the flow to rerun. 2. Flow State Management: Ensure that the flow's state transitions are managed correctly. If a flow is marked as incomplete or in a non-final state, it might be retried or rerun unintentionally. 3. Concurrency and Priority Settings: If using work pools or queues, verify that concurrency and priority settings are not causing unexpected behavior. Prefect's documentation on work pools might be helpful. 4. Known Issues: Review known issues on Prefect's GitHub repository, as there might be bugs related to duplicate or unexpected flow executions. If these steps don't resolve the issue, consider reaching out to Prefect support or the community for more personalized assistance.