I'm seeing odd behavior with the script below. It's producing many flow runs(I'm expecting one) and none of the tasks are being run(they're omitted from the code block example). fwiw, the script is being run inside a lambda container. This lambda is being triggered from an event produced by a different lambda. Any ideas?

def handler(event: dict, context: LambdaContext):
    """This function is the entry point for the Lambda function"""

    <http://log.info|log.info>("starting lambda function for artist ranking")

    <http://log.info|log.info>(f"event: {event},context: {context}")

    start = time.time()

    deployment = Deployment.build_from_flow(
    flow=artist_ranker_etl,
    name="artist-ranker-deployment"    
    )
    deployment.apply()
        

    run_deployment(name="artist_ranker_staging/artist-ranker-deployment",tags=["staging","ranker"])
    
    
    end = time.time()
    
    print(f"Time to execute: {end - start}")

Is there a reason why you are building and applying the deployment from inside the lambda?

It seemed the appropriate place to put it, which is with the service logic. Is there an alternative best solution? The flow run seems to register with the cloud api server but doesn't seem to be finishing execution, none of the task details are showing up. I'll send you a screenshot when I get to a place, in transit right now.

oooooh

hmm, I don't think so. Can I add a line to the script to set up the agent?

Hey Zach, I'm not terribly familiar with Lambda, but I do have some thoughts on how to set up the agent. You could try creating a bash script that contains the

prefect agent start -p "work-pool-name"

command. Then, you can trigger the bash script to run from within the lambda function. The bash script would look something like:

#!/bin/sh
prefect agent start -p "work-pool-name"