# Build and deployment issues

## Cloud build fails with object errors

Possible cause

One or more objects could not be created in Qlik Sense. The console displays `Build failed` followed by a description of the error. The failure typically occurs when an object property is not supported by the target visualization type.

Proposed action

Open the app in Qlik Sense to review the affected objects. The app is created and most objects are loaded successfully. Check the Excel conversion report for objects with an Error outcome. These objects require manual correction in the Qlik Sense app editor. Review the per-run log file in the `logs/` output subfolder for the full error details.

## Media upload fails

Possible cause

One or more image files could not be uploaded to the Qlik Sense media library. The console displays `Media upload failed for N/M file(s)` followed by the first failure detail.

Proposed action

Verify that the image files exist and are not corrupted. Check the file sizes, as very large images may exceed upload limits. Retry the deployment. If the issue persists, upload the images manually through the Qlik Sense media library. Run with `--logLevel DEBUG` to identify which files failed in the log output.

## Temporary auto-binary app remains after a failed deployment

Possible cause

The build or reload step failed after the QVW file was uploaded to Qlik Cloud. QV2QS attempts to delete the temporary app automatically, but cleanup may fail if the network connection is interrupted or the API key has expired.

Proposed action

Check the target space for apps named `QV2QS_Binary_YYYYMMDD_HHMMSS` (for example, `QV2QS_Binary_20260219_143025`) and delete them manually. Re-run the conversion to regenerate the output files. Review the per-run log file in the `logs/` output subfolder for cleanup error details.

## Sheets disappear after redeploying to an existing app

Possible cause

The sheet preparation step failed partway through. QV2QS removes existing sheets from the cloud app before building so that the new sheets can be created with the same IDs. If the removal or build step fails, the app may be left in an incomplete state.

Proposed action

Restore the app from the automatic pre-deploy backup. Backups are saved to `cloud/backups/` in the project output folder. Import the backup QVF into the target space through the Qlik Cloud hub. Then re-run the deployment. If no backup is available, re-run the conversion as a new app by omitting `--reuseAppId` and `--appId`.

## New sheets are not published after redeploying to an existing app

Possible cause

The Publish sheets setting was disabled during the redeployment. When reusing an existing app, QV2QS restores the publish state of previously deployed sheets automatically, but new sheets are only published when the Publish sheets setting is enabled.

Proposed action

Re-run the deployment with Publish sheets enabled (the default). Alternatively, publish new sheets manually in Qlik Cloud. Open the app, right-click each unpublished sheet, and select Publish.

## Learn more

* [Build and deployment](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/deploying-to-qlik-cloud/build-and-deployment.htm)
* [Reusing an existing app](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/deploying-to-qlik-cloud/reusing-an-existing-app.htm)
* [Qlik Cloud resource limits](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/known-limitations/qlik-cloud-resource-limits.htm)
* [Conversion report](https://help.qlik.com/en-US/migration/Content/Qv2qsMigration/conversion-results/conversion-report.htm)