error code 135, Internal Server Error:Failed to submit job on instance pool. Integration Runtime

Question

SR ID : 2212140060000901

Using an Azure managed virtual network, a data flow that was running fine until 2 days ago is not running since yesterday.
Change Azure IR to Azure public network 'AutoRsoloveIntegrationRuntime' and run normally when run.

Internal Server Error:Failed to submit job on instance pool. Integration Runtime.
When using the technical support solution with the runtime ID, answer are prompted to contact the support team.
*Korea central region.

"You are impacted by an intermittent issue, please set retry to protect against such intermittent issues. Learn how to put retry .
If the problem still persists, please contact support.
Provided input is - efc6df33-5bbb-47df-9cd9-b354d5283b09"

Answer 1

Hello @최이현 ,

As per the analysis from support ticket below are suggestions provided by internal product team to overcome this problem

2. Regarding the "Internal Server Error". Usually, Internal server errors are the backend issue and will be auto resolved within a shorter time automatically.
3. For Transient errors it is recommended to use "Retry" settings which would fix the issue. Please note If we set the "re-try" for the whole Dataflow, there is a chance that the data will be duplicated as all the activities in the dataflow will re-run again. Hence, we have 2 options to set re-try and not to duplicate the data. a. We have to set the re-try for the activity which is failing So that only the failed activity will re-try.
   b. Or we can re-run from the failed activity manually in the monitor Tab.
4. If you're seeing the "Hit Exception" error. We request you to select the "Memory Optimized" with high core count to fix the issue.

Hope this info helps.

------------------------------

• Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how