ArcGIS Pro 2.5: How to overwrite outputs of geoprocessing tools when run in a model builder?

[JamalNUMAN]

ArcGIS Pro 2.5: How to overwrite outputs of geoprocessing tools when run in a model builder?

Despite the fact that “Allow geoprocessing tools to overwrite existing datasets” option is checked, outputs appear not be overwritten when working with model builder.

What could be the issue here?

[wayfaringrob]

Facing the same issue in Pro 3.3.1 - I have a model built that I would like to use to refresh a map layer, but it seems that each and every time, I need to delete the output layer first -- despite having toggled the overwrite in settings.

[Markbe_utco]

Bump topic.  Experiencing the same issue.

Yes, I understand that converting the model to a python script and adding arcpy.env.overwriteOutput = True will work.  I'd like to make sure the model actually works before I convert it python script.  Why is there no way to overwrite a feature class when a tool is run within ModelBuilder?

[Kevin_MacLeod]

bump. It's 2025, still an issue.  I had expected to see that as an option in Environments for a step in a tool. I am circling back after a long time, to using ModelBuilder and will be relying on it heavily.  Definitely a significant issue. Also, one I would imagine is trivially solved in the code by the Esri devs. Simply implement that python line setting that Boolean under the hood, so it works in the ModelBuilder GUI.  This would eliminate the laborious step of deleting all layers at each step of the way when necessary, every time, every model, that we have to add 

Each tool or step should have this setting Environments, Overwrite. I opened this up for clip today for example and expected it to be there.  I'm aware of the global Env in Pro but models should have this so they can override it and be re-used across orgs by other users without having to ask them to change any Env settings.