Forum Discussion

smeetsh's avatar
smeetsh
Icon for Continued Contributor rankContinued Contributor
13 hours ago

SQL Endpoint lakehouse: Intermittent error in the Refresh SQL analytics endpoint activity

Hi All, since Monday we are having intermittent issues with the Refresh SQL analytics endpoint in our pipelines in fabric.  We run multiple pipelines on an F8 sku, which Monday was about 60% used an...
data pipeline
lakehouse
v-sathmakuri's avatar
v-sathmakuri
Icon for Community Support rankCommunity Support
7 hours ago

Hi smeetsh​ ,

Thank you for reaching out to fabric community.

  • This is most likely a transient Fabric API timeout not an F8 capacity issue.
  • Add a Retry policy with a delay to the Refresh SQL analytics endpoint activity.
  • Ensure the activity runs after all Lakehouse write / ingestion operations are completed to avoid concurrent update / locking issues.
  • Microsoft's current documentation specifically states that the activity can intermittently fail when other processes are actively updating the underlying Lakehouse, because the SQL analytics endpoint needs to acquire internal locks. However, the exact 408 Request Timeout / A task was canceled error in your example is not explicitly documented as the known issue.

Refresh SQL analytics endpoint activity - Microsoft Fabric | Microsoft Learn

Thanks!!