Error Code: 9518

[Ghobinath]

trying to do a lookup from my onpremise service, gateway is up dataflow gen 2 works, in pipeline i hit this issue.
The Data Factory runtime is busy now. Please retry the operation later.
was working fine past few days.

[deoryadav]

@Ghobinath -

I am experiencing the same issue while setting up a pipeline with the Lookup activity. When I test the connection, I get the error:

Error Code: 9518

'The Data Factory runtime is busy now. Please retry the operation later.'

One approach I tried was increasing the integration runtime's node size from the default configuration, specifically while ingesting on-prem data into the Lakehouse. After adjusting the node size, the issue was resolved for me. You may want to give this a try as well.

[Ghobinath · Accepted solution]

Hi, do you mind sharing how you did this? For my issue when I changed the gateway to another node it solved the problem. I assume it's gateway problem.

[v-vpabbu]

Hi @Ghobinath,

Thanks for sharing your update and confirming that the issue is resolved. Could you please accept your own post as a solution? It will be helpful for other members of the community facing similar problems to resolve it faster.

Regards,

Vinay Pabbu

[v-vpabbu]

Hi @Ghobinath,

Thank you for reaching out to Microsoft Fabric Community Forum.

Error 9518 usually means the Fabric Integration Runtime (IR) is overloaded or unresponsive. Since it's been ongoing for hours even after scaling to F4, it's likely a backend issue — possibly IR saturation in your region.
If you're a Fabric admin, check IR usage metrics for any spikes.

I recommend raising a support ticket with Microsoft to get it looked into.
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Regards,
Vinay Pabbu

[Ghobinath]

We have scaled from F2 to F4 but the issue persists — all pipelines continue to return Error 9518. This confirms that it's not capacity-related but likely a Fabric backend IR issue.

[Ghobinath]

To addon im in GMT+8 zone and in Asia Pacific region.

[Ghobinath]

Just to note, this is still ongoing as of 9:08 stuck for the past 4 hours, tried restarting fabric, created new connection. nothing works. lookup able to connect within fabric sql it self. – appreciate any help!