Hi, when running on ECSRun and setting env variables they are auto casting strings to ints which causes boto3 exception, is there a way to avoid auto casting?

Hey @Nadav, is this when setting env vars on the agent? or through the RunConfig?

@Kevin Kho i set the variables on the cloud ui when creating a run

Can you reproduce this with a minimal flow example? Does it also happen with Local Agent for you?

it won’t happen in local agent since this as far as i know an AWS exception when submit env variables to ECS, the type of of the variables values should be strings

Ohh gotcha! I’ll try to replicate this tonight.

thanks

I replicated this. So when I go to the UI and do key=test, value=1, this becomes an integer but if I do key=test and value=“1” and this worked. When I used JSON to input though, automatic conversation was applied. Will talk to the team about this.

thanks, i will try the solution without json

I opened an issue for this here: https://github.com/PrefectHQ/ui/issues/979

Thank you