Copy case works (create case from local action submit) well if launched from step which is not in screen flow but if the same local action is performed in any step of the screen flow this results in error on UI “An internal error occurred. Please contact administrator. “but in background i can see new copy of the case is created without any issue. Any suggestions?
This looks like a screen flow UI state issue, not a Copy Case failure, because the new case is still getting created in the background. Pega handles local actions differently inside screen flows, and recent resolved issues also show known problems around screen flow navigation, validation, and local action submit behavior. The clean solution is to move the Copy Case action out of the screen flow and run it from a normal flow step or a separate non-screen-flow assignment. That avoids the screen flow refresh/state conflict and lets the copied case open correctly without the internal error.