It is not paying attention what is doing when restoring data from local sql server db to azure sql database

Open 💬 0 comments Opened Jun 22, 2026 by mibrowtito

Preflight Checklist

  • [x] I have searched existing issues for similar behavior reports
  • [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

i have requested claude to take a bakup of local sql server db and restore on azure db because there was a discrepancy in the data caused by some issue it found. It started and at the end it found it took the backup from the azure and reload the same data. then i requested to do it again, it started but left all cron jobs running causing that when it was restored the data got contaminated again, for the 3rd time i request to restore everything again and i hope it does it correct. this has make me loose wait and waste the tokens.

What Claude Actually Did

i have requested claude to take a bakup of local sql server db and restore on azure db because there was a discrepancy in the data caused by some issue it found. It started and at the end it found it took the backup from the azure and reload the same data. then i requested to do it again, it started but left all cron jobs running causing that when it was restored the data got contaminated again, for the 3rd time i request to restore everything again and i hope it does it correct. this has make me loose wait and waste the tokens.

Expected Behavior

it was supposed to stop all processes accessing azure db, take backup from local db, then restore the azure db, and then restart all process afecting the db.

Files Affected

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

_No response_

Claude Model

Sonnet

Relevant Conversation

Impact

Critical - Data loss or corrupted project

Claude Code Version

sonet 4.6

Platform

Anthropic API

Additional Context

_No response_

View original on GitHub ↗