Forum Discussion

SimoneZier's avatar
SimoneZier
Regular Visitor
9 months ago
Solved

Error message "RequestValidationFailed" when attempting to modify a copy job by the owner

Dear all,   we face the problem that it is not possible to save changes in a copy job which is not originally created by ourselves, but we get the error message: RequestValidationFailed The goal i...
data engineering
data pipeline
lakehouse
  • v-venuppu's avatar
    v-venuppu
    8 months ago

    Hi SimoneZier ,

    Thank you for reaching out to Microsoft Fabric Community.

    Thank you tayloramy  for the prompt response.

    This is an issue with Fabric Copy Jobs: even after you “Take Over” a job, the system still keeps the original creator tied to the job internally. Because of that, certain changes-like switching from append to overwrite-can only be made by the person who originally created the job.
    That’s why your new jobs (where you are the creator) work, but taken-over jobs fail with RequestValidationFailed.
    The only reliable workaround today is to recreate the copy job under your own account. Microsoft is aware of this limitation and a fix is expected in a future update.

v-venuppu's avatar
v-venuppu
Community Support
8 months ago

Hi SimoneZier ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you tayloramy  for the prompt response.

This is an issue with Fabric Copy Jobs: even after you “Take Over” a job, the system still keeps the original creator tied to the job internally. Because of that, certain changes-like switching from append to overwrite-can only be made by the person who originally created the job.
That’s why your new jobs (where you are the creator) work, but taken-over jobs fail with RequestValidationFailed.
The only reliable workaround today is to recreate the copy job under your own account. Microsoft is aware of this limitation and a fix is expected in a future update.

SimoneZier's avatar
SimoneZier
Regular Visitor
8 months ago

Thank you very much for your detailed feedback v-venuppu. It's good to know that we're not doing anything wrong, but that there is simply a bug here, which Microsoft is already aware of and will fix in a future update.