Forum Discussion
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 is to change the update method of the copy job from "append" to "overwrite". As soon as we want to apply the changes, we get the error message RequestValidationFailed
Additional information / details:
- copy mode is "full copy"
- source is a sql server
- target is a fabric lakehouse
- if the user who originally created the copy job does the changes, it works fine
- if anyone else (also Admin of workspace and target lakehouse) tries it, it does not work but the error message appears, even if the person takes over the ownership of the job
- if we do changes in some other objects (dataflow, pipeline etc.) everything works fine
Does anyone have any ideas what the reason for the error could be or what we need to adjust? Or could this be a bug?
Does anyone else have the same problem?
Thank you in advance for your ideas and support and best regards
Simone
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.
8 Replies
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.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.
Hi SimoneZier,
Before making changes, you should take over the copy job. Go to the settings page, and then if you are not the owner there will be a take over button:
Once you take over, then you are the owner and can make all changes.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Thanks tayloramy for your answer. I have already taken over the copy job and I am the owner but it still doesn't work 😞 Any other ideas?
Hi SimoneZier,
Do you have permissions on all the connections that are used?
Are there any gateway connections being used?
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi tayloramy ,
yes, I have full access (admin) of all used connections / gateways.
If I create a copy job with the same connections and settings, everything works fine. We therefore have two identical jobs, with the only difference being that in one case, I am the creator, and in the other case, I am only the owner. If I am the creator, all changes work. If I am only the owner, I receive the error message.
Best regards
Simone
Hi SimoneZier ,
I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.
Thank you.
I received the same error when changing a pipeline from a lakehouse to a warehouse connection in the the Lookup activity. The query in the activity runs successfully when reviewing the data, though it fails during saving. I compared the two versions side by side and I don't see any meaningful differences between the two versions. It just doesn't make sense?!
The way it looks, the dependency check seems to be done outside of pipeline's definition.
For troubleshooting purposes I took only the minimum of code and still doesn't work. Same result when I started from scratch with the warehouse.
