Repair broken link for raster function?

[DavidField]

Is it possible to repair a broken link for a raster created using the Raster Functions menu (e.g slope, multidirectional hillshade)? 

For a normal raster it's simply a matter of clicking the exclamation point and directing it to the file it's looking for, however with a raster function, it's source is the same as the raster it was created from. But if you point it to that raster you won't get the slope or hillshade you created previously, you'll just get a uniform grey mask.

[collbett_geomorph]

Same problem and it is happening frequently in ArcPro 3.2.2.  Please post something about a fix or I'll have to give up using raster functions in any project that I need something like a hillshade to persist between sessions.

[CarlVon_Stetten1]

I'm seeing a similar issue with raster layers that have no raster functions applied - just plain raster mosaic layers.  Other non-raster layers on the map do not load properly until the repair is done on the raster layers.  This happens whenever I open my Pro project.

[WJWalko]

This works:  Make a persistent copy of the "transient" .afr file which is used for the raster-function output layer.

The output layer from the raster function is stored as an ".afr" file in ArcGIS's temporary workspace, as defined by Windows <TEMP> variable.  One can identify the specific file by right-clicking the raster-function output layer, select "Data"->"Add to Mosaic Dataset".  The specific .afr file will then be displayed in the Geoprocessing pane (see attached graphic).  One can then manually copy the "temporary" .afr file to a more "persistent" location, and give it a meaningful filename.  Lastly, change set "Properties"->"Source" of the raster-function layer to use your new "persistent" .afr file, instead of the original .afr file which is stored in temporary workspace.

[ChristopherMyers]

Thanks! This worked for me

[DuncanHornby]

I wish to add to this thread and say I too have experienced this problem in past versions of ArcPro and also the very latest (3.5). It's really frustrating and makes using raster functions a pointless endeavour when the next time you open your project the layer is broken.

@KoryKramer can you give the team behind raster functions a prod to ensure  they are at least looking into the issue.  A simple use case scenario is load a DEM, run the hill shade raster function, admire the beauty of it, save the project, close arcpro, open arcpro, hey presto hill shade layer is broken.  No one should be implementing the work around that @WJWalko  has suggested. Or if this is an issue that cannot be fixed because of how raster functions work, then a warning in help file with advice outlining @WJWalko  approach would be helpful.