# Automation/job yaml file configuring

**URL:** <https://forum.pioreactor.com/t/automation-job-yaml-file-configuring/676>\
**Category:** API & Data Access\
**Created:** [February 23, 2025, 3:16pm UTC](https://forum.pioreactor.com/t/automation-job-yaml-file-configuring/676 "2025-02-23T15:16:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rafik.n](https://forum.pioreactor.com/letter_avatar_proxy/v4/letter/r/e95f7d/32.png) [@rafik.n](https://forum.pioreactor.com/u/rafik.n)\
**Post date:** [February 23, 2025, 3:16pm UTC](https://forum.pioreactor.com/t/automation-job-yaml-file-configuring/676/1 "2025-02-23T15:16:40Z")

</div>

Hey @CamDavidsonPilon,

Hope youre doing well.

Quick question for you. Been chasing a bug in a custom dosing automation subclass I wrote. I had used the same name(variable) in the yaml file for the job name and one of the published setting -key that i wanted to load into the automation via the gui.

This did not produce any errors but instead just did not load the value into the code when I changed it when starting job using the gui and defaulted to the click command default value.

All that said, I stumbled on the answer was to change the key name to something else but I do not know why this worked. Can you point me in the right direction on how the flow works regarding the interpretation/loading of yaml file variables?

Thank you!

---

<div class="post-metadata">

**Author:** ![CamDavidsonPilon](https://forum.pioreactor.com/user_avatar/forum.pioreactor.com/camdavidsonpilon/32/3_2.png) [@CamDavidsonPilon](https://forum.pioreactor.com/u/CamDavidsonPilon)\
**Post date:** [February 24, 2025, 3:53pm UTC](https://forum.pioreactor.com/t/automation-job-yaml-file-configuring/676/2 "2025-02-24T15:53:44Z")

</div>

Hi @rafik.n,

Hm, I’m not sure what is causing the original issue.

The UI automation dialog is populated by this endpoint: `/api/contrib/automations/<automation_type>` - it just converts yaml files to a big json blob.

When starting an automation, the UI sends a web request to `/unit_api/jobs/run/job_name/<job>` [here](https://github.com/Pioreactor/pioreactorui/blob/master/pioreactorui/unit_api.py#L244-L282), and that converts some GET parameters to CLI parameters. Then that creates a background task [here](https://github.com/Pioreactor/pioreactorui/blob/master/pioreactorui/tasks.py#L79-L87) to be run.