Ok so your dag should not do any triggering. dag file should just define dag.
so remove any `os.*` stuff. don't need to mess with globals. make sure your dag file is in dags folder in terminal you can do `airflow info | grep dags_folder` to see what the current configured dags folder is you can test that your dag parses correctly with `python /path/dagfile.py` if no errors there, and it's in your dag folder you should be good. next check do `airflow dags list`. you should see it there. next you can trigger from CLI with `airflow dags trigger` or something like that. but scheduler must be running already for this to work. otherwise trigger from UI. before starting webserver, in the terminal wher you will start it, check that you can see the dag with airflow dags list. don't trigger the dag from the dag file itself.
