Extraction error: Config transforms failing
Last updated
Was this helpful?
Last updated
Was this helpful?
Sometimes you might notice that even though your deployments are coming through without errors, no changes are being applied to the Cloud environments. This might be due to Config Transforms failing during the extraction process.
This issue may occur if you have added custom to your project.
Since Config Transforms are applied on every data extraction, the behavior will continue until the Config Transform files are either corrected or removed.
This problem is a bit tricky to spot, as the only indicator is that changes you made on the source environment are not being applied - even though the deployment was complete (although when pushing from local you might get a warning message).
The environment overview on your project will most likely not mention anything, which means you will have to delve into KUDU.
Access on the environment where you expected to see your changes reflected
Navigate to site > deployments folder in KUDU
Find the latest deployment folder, either by date or by ID of the deployment (you can find the latest active deployment ID by opening the active file in the folder)
If the deployment folder with the latest ID contains only two items (log.log
and status.xml
), that means something went wrong as we would normally see two more files - commits.uc
and manifest
Open the log.log
file and look for anything mentioning XmlTransform
.
An example of a faulty config transform not being applied could look something like this:
Verify the Config Transform file mentioned in the error message and ensure the XML is valid.
Update the Config Transform file as necessary on your local solution and deploy the change to the Cloud environments.
Run a to extract the schema that you previously deployed.