ArcGIS Pro 3.4.2: “The table was not found” error appears frequently without a clear reason,

[JamalNUMAN]

ArcGIS Pro 3.4.2: “The table was not found” error appears frequently without a clear reason,

I’ve observed that Model Builder is frequently filled with errors when using version 3.4.2. The “The table was not found” error is just one example of the recurring issues that have become almost a daily struggle.

What could be causing this?
Could it be a bug?

[DanPatterson]

punctuation and/or spaces amd really long path names are an issue, not just with ArcGIS Pro, but particularly is you are working with rasters. 

Is it possible that your output is an esri grid? (ie.  You didn't specify a *.tif file extension for the folder destination)

Grids don't like long paths and particularly long filenames.

Is H a local drive?  Try inputs and outputs to local folders with shorter paths.  Move/copy later if needed.

Details of the paths rather than screen grabs would help too

[JamalNUMAN]

Thank you for the input.

1. The name of the output is generated automatically, and I don’t change it.

2. I don’t modify the raster’s extension; it is created automatically.

3. I’ve observed that the issue occurs even when the file path is short.

4. Drive H is a local drive.

Two observations:

1. This issue did not exist during the ArcMap era.

2. Sometimes, the issue disappears without making any changes at all!

[DanPatterson]

I would have a look at your path naming practice.  In the last image the path length is still very long and it still contains brackets (eg ....Environment_(01) ) and the input raster name has both spaces and brackets.

[JamalNUMAN]

Why should this be an issue? And why does it work sometimes but fail at other times?

[DanPatterson]

keep trying those long paths with ( ) in them and see if it eventually works, or try a folder that is simpler, for instance

H:\output\some.gdb\short_name

[JamalNUMAN]

This error appears to have nothing to do with either the name or the path of the input/output folders, as shown in the screenshot below.

[DanPatterson]

refresh catalog or reboot and check again to see it is there

[JamalNUMAN]

It’s as if ArcGIS Pro has no consistent behavior when working with model builder. This frustrating error is illogical and frequently appears without any clear reason.