https://community.esri.com/t5/arcgis-pro-questions/c-debugging-arcgis-pro-3-0-queued-task/m-p/1261402#M65897 <P>Hello,</P><P>I've recently upgraded from ArcGIS Pro 2.8 to 3.0.&nbsp; When debugging in 2.8, breakpoints inside a QueuedTask would give an error along the lines of "Wrong thread, click to force a refresh." I would be able to force a refresh and see whatever data I was trying to debug.</P><P>In 3.0, this force refresh option is not available. Instead, I see "Evaluation is not allowed: The thread is in stack overflow state."</P><P>Note that none of the underlying code changed outside of adding a few "Ex" to builders and "Type" to enums values.</P><P>Is this expected? The ability to easily debug inside a QueuedTask was fantastic in 2.8, I hope there is a workaround for 3.0.</P><P>Thanks!</P> Fri, 24 Feb 2023 14:25:58 GMT bland 2023-02-24T14:25:58Z https://community.esri.com/t5/arcgis-pro-questions/c-debugging-arcgis-pro-3-0-queued-task/m-p/1261402#M65897 <P>Hello,</P><P>I've recently upgraded from ArcGIS Pro 2.8 to 3.0.&nbsp; When debugging in 2.8, breakpoints inside a QueuedTask would give an error along the lines of "Wrong thread, click to force a refresh." I would be able to force a refresh and see whatever data I was trying to debug.</P><P>In 3.0, this force refresh option is not available. Instead, I see "Evaluation is not allowed: The thread is in stack overflow state."</P><P>Note that none of the underlying code changed outside of adding a few "Ex" to builders and "Type" to enums values.</P><P>Is this expected? The ability to easily debug inside a QueuedTask was fantastic in 2.8, I hope there is a workaround for 3.0.</P><P>Thanks!</P> Fri, 24 Feb 2023 14:25:58 GMT https://community.esri.com/t5/arcgis-pro-questions/c-debugging-arcgis-pro-3-0-queued-task/m-p/1261402#M65897 bland 2023-02-24T14:25:58Z