sqlEndPoint metadata refresh

[smpa01]

curl -X POST \
  "https://api.fabric.microsoft.com/v1/workspaces/<ws_id>/sqlEndpoints/<sql_enddpoint_id>/refreshMetadata" \
  -H "Authorization: Bearer <your-access-token>" \
  -H "Content-Type: application/json" \
  -d '{"timeout": {"timeUnit": "Minutes", "value": 10}}'

I keep on getting Response code 200, I was expecting 202.

As a result, I am getting

{
  "value": [
    {
      "tableName": "test",
      "status": "NotRun",
      "startDateTime": "2025-07-31T00:07:15.0306056Z",
      "endDateTime": "2025-07-31T00:07:15.5150298Z",
      "lastSuccessfulSyncDateTime": "2025-06-05T02:29:01.543114Z",
      "error": null
    }]}

Why is it only returning TableSync Status and not triggering a refresh?

Do I understand that I need to make the service call immediately following a transaction such as following? Else it will show as NotRun if the background jobs deems it is not necessary to refresh the metadata?

def acid_transaction():
    # do something
def refresh_metadata ():
    # refresh metadata

# pseudo workflow
acid_transaction()
   ↓
refresh_metdata()
         

[v-veshwara-msft]

Hi @smpa01 ,

Following up to see if your query is resolved and if any of the responses helped.
If you're still facing issues, feel free to reach out.

Thank you.

[v-veshwara-msft]

Hi @smpa01 ,
Just wanted to check if the responses provided were helpful. If further assistance is needed, please reach out.
Thank you.

[v-veshwara-msft]

Hi @smpa01 ,

Just checking in to see if you query is resolved and if any responses were helpful.
Otherwise, feel free to reach out for further assistance.

Thank you.

[v-veshwara-msft]

Hi @smpa01 ,

Thanks for sharing this in Microsoft Fabric Community.
As mentioned by @lbendlin , the behavior you're seeing is expected. The refreshMetadata call checks if a refresh is needed based on recent changes, and if it determines that there's no schema change or update requiring sync, it completes with a 200 response and status as NotRun.

This means the service has received the request but didn't find any reason to run the refresh job.

As you pointed out, if the preceding transaction didn't introduce any structural changes to the table, this outcome is expected.

Blog Reference : Refresh SQL analytics endpoint Metadata REST API (Generally Available) | Microsoft Fabric Blog | Mic...

Please reach out for further assistance.

Thank you.

[lbendlin]

it believes that a refresh is not necessary in the current circumstances.