The Lazarus process is meant to gracefully retry failures caused by factors outside of Prefect's control. The most common situations requiring Lazarus intervention are infrastructure issues, such as Kubernetes pods not spinning up or being deleted before they're able to complete a run.

Once every 10 minutes, the Lazarus process searches for distressed flow runs. Each flow run found in this manner is rescheduled; this intervention by Lazarus is reflected in the flow run's logs.

date

CronSchedule()

CronSchedule("00 02,12 * * *", start_date=pendulum.now("Europe/Berlin"))

date=pendulum.today("Europe/Berlin")

mutation {
  set_flow_group_schedule(input:{
    flow_group_id: "f67a1118-41e6-4e3b-9f14-9203e8f5ed55",
    interval_clocks: [
      {interval: 60 
       parameter_defaults: {my_param: "my_param_value"}
      }
    ],
    timezone: "America/New_York"
    }
  ) {success}
}

requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http://{endpoint}:80/graphql/alpha

database = prefect.context.get("database", "JOYN_SNOW_BI_1841")

prefect server start

docker-compose up

docker-compose.yml

prefect server config

prefect server config

prefect server config

prefecthq/prefect:latest

prefect server create-tenant

Run a flow that is registered to the Prefect API

Options:
    --id, -i                    TEXT        The ID of a flow to run
    --version-group-id          TEXT        The ID of a flow version group to run
    --name, -n                  TEXT        The name of a flow to run
    --project, -p               TEXT        The name of a project that contains the flow
    --version, -v               INTEGER     A flow version to run
    --parameters-file, -pf      FILE PATH   A filepath of a JSON file containing
                                            parameters
    --parameters-string, -ps    TEXT        A string of JSON parameters (note: to ensure these are
                                            parsed correctly, it is best to include the full payload
                                            within single quotes)

storage.directory

storage.directory

prefect server start

docker-compose.yml

prefect server config

docker-compose.yml

<http://localhost:4200>

http://<server IP>:4200/

docker-compose.yml

docker-compose.yml

config.toml

prefect server start

docker-compose.yml

prefect server start

config.toml

host=

config.toml

host=127.0.0.1

--no-hasura-port

--no-postgresql-port

python3 -m venv prefect_venv
source prefect_venv/bin/activate
pip install wheel
pip install prefect
prefect backend server
prefect server start

prefect diagnostics

{
  "config_overrides": {},
  "env_vars": [],
  "system_information": {
    "platform": "Linux-4.15.0-142-generic-x86_64-with-Ubuntu-18.04-bionic",
    "prefect_backend": "server",
    "prefect_version": "0.14.16",
    "python_version": "3.6.9"
  }
}

RuntimeError: 
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.