Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

[Cristian_Galindo]

I am using ArcGIS Pro 2.9, and trying to make some basic spatial operations.

Two sets of features were selected from a geodatabase, and using them, an intersection will be performed.

As it is not intended to persist this objects, the script use the "in_memory" workspace (it was done for the version 2.1 thinking in ArcDesktop).

Today, in an attempt to update the script with the new characteristics of the version 2.9, I found that the intersect tool does not like the memory workspaces.

Here is my evidence:

reading the documentation of the intersect tool, it does not mention a restriction for this kind of datasets.

Is this a bug? How do I report it?

[HannesZiegler]

@Cristian_Galindo are you able to contact Technical Support Services? They will be able determine whether this is a bug and can file an internal issue if it is.

[JoshuaBixby]

Have you checked whether the issue is with selecting?  If something isn't working correctly with Select, it may be there isn't anything selected for Intersect to operate on.

[Cristian_Galindo]

As I posted as evidence, both scenarios are the same, the only difference is the location of the expected result. but in order to provide more evidence, i ran the scripts against an smaller dataset, and print the results:

[Cristian_Galindo]

After some trial and error (not you pity documentation) I found that Intersect tool does not like "memory" (modern, state of the art) workspaces as INPUT, it does not care about the output:

[Cristian_Galindo]

Additional Note:
The tool MakeRouteEventLayer does not like either the "memory" workspaces as input.

The documentation: https://pro.arcgis.com/en/pro-app/2.9/tool-reference/linear-referencing/make-route-event-layer.htm 

does not state this.