Setting up new space with GitHub -- trouble in paradise

đź’¬ App Building
,
1

My goal: Connect a new retool “space” to our github repo, to migrate/import apps and resources (retool cloud, enterprise edition)

Issue: Deploy failed

  • The retool interface reports “Deploy failed · Next attempt in 2 hours... Will continue to retry at 1 min, 5 min, 30 min, 2 hrs, 8 hrs, then every 24 hrs until resolved.”

Steps I've taken to troubleshoot:

  • “connected” shows as green in /settings/source-control
  • “view logs” indicates a zipfile corruption under the hood? See below

Additional info: (Cloud, Enterprise)

So we just created a new retool space with a new subdomain. We’re hoping to connect to github, as we have with other spaces, to pull down resources and apps.

Here’s a section of Retool’s “view logs” output. It lists apps and resources okay at the top, then progresses down to…

[2026-05-28T21:13:48.255Z] Retrieving AGENT contents to deploy.[2026-05-28T21:13:48.256Z] Identified 0 Retool AGENT:

[2026-05-28T21:13:48.256Z] Retrieving TRANSLATION contents to deploy.[2026-05-28T21:13:48.257Z] Identified 0 Retool TRANSLATION:

[2026-05-28T21:13:48.257Z] Retrieving THEME contents to deploy.[2026-05-28T21:13:48.258Z] Identified 0 Retool THEME:

[2026-05-28T21:13:48.340Z] Assembling app/module content: "dist/apps/17ad971e-658e-11ef-b707-6b7782480772/0.2.12.zip".[2026-05-28T21:13:48.568Z] Assembling app/module content: "dist/apps/45a99608-5ced-11ef-91fc-cbe149dbc066/0.4.12.zip".[2026-05-28T21:13:49.029Z] Unknown runSync failure (GitHub): End of data reached (data length = 257208, asked index = 305779). Corrupted zip ?Error: End of data reached (data length = 257208, asked index = 305779). Corrupted zip ?at NodeBufferReader.checkIndex (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/reader/DataReader.js:26:19)at NodeBufferReader.checkOffset (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/reader/DataReader.js:17:14)at NodeBufferReader.readData (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/reader/NodeBufferReader.js:14:10)at ZipEntries.readBlockEndOfCentral (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/zipEntries.js:59:38)at ZipEntries.readEndOfCentral (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/zipEntries.js:177:14)at ZipEntries.load (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/zipEntries.js:255:14)at /retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/load.js:48:24at async ReleaseArtifact.fromZip (/retool/backend/backend-oci.runfiles/_main/backend/src/server/modules/releases/releaseArtifact.js:88:25)at async retrieveReleases (/retool/backend/backend-oci.runfiles/_main/backend/src/server/modules/syncWithGit/retrieveReleases.js:126:33)at async runFullSync (/retool/backend/backend-oci.runfiles/_main/backend/src/server/modules/syncWithGit/index.js:220:69)[2026-05-28T21:13:49.284Z] RunSync failure (GitHub): End of data reached (data length = 257208, asked index = 305779). Corrupted zip ?Error: End of data reached (data length = 257208, asked index = 305779). Corrupted zip ?at NodeBufferReader.checkIndex (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/reader/DataReader.js:26:19)at NodeBufferReader.checkOffset (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/reader/DataReader.js:17:14)at NodeBufferReader.readData (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/reader/NodeBufferReader.js:14:10)at ZipEntries.readBlockEndOfCentral (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/zipEntries.js:59:38)at ZipEntries.readEndOfCentral (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/zipEntries.js:177:14)at ZipEntries.load (/retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/zipEntries.js:255:14)at /retool/backend/backend-oci.runfiles/_main/node_modules/.aspect_rules_js/jszip@3.10.1/node_modules/jszip/lib/load.js:48:24at async ReleaseArtifact.fromZip (/retool/backend/backend-oci.runfiles/_main/backend/src/server/modules/releases/releaseArtifact.js:88:25)at async retrieveReleases (/retool/backend/backend-oci.runfiles/_main/backend/src/server/modules/syncWithGit/retrieveReleases.js:126:33)at async runFullSync (/retool/backend/backend-oci.runfiles/_main/backend/src/server/modules/syncWithGit/index.js:220:69)

I can see on github.com that dist/apps/…/0.4.12.zip exists, plus 0.4.13.zip also exists in that directory. I’m not familiar with the machinations backstage, on how these zips get created.

Is there a procedure we can engage in, on our main admin “space” to fix this?

3

Hey @trillich - thanks for reaching out. I'm guessing that this is just the lingering effects of a bug that we previously addressed. :thinking: If so, the solution is to correctly regenerate the corrupted zip files.

Let's try the following:

  1. In an existing space, open the app with a UUID of 45a99608-5ced-11ef-91fc-cbe149dbc066.
  2. Make and merge a small change in order to regenerate the zip artifact.
  3. Retry the deploy within the new space.

It's possible that there are other affected artifacts, though. Do you mind sharing the full deploy logs so that we can confirm? Feel free to DM me!

4

So we did two things, at least one of which resolved the issue :face_savoring_food:…

  1. delete the corrupt .zip files (there were several) via github.com after some checking to develop confidence that no “spaces” were depending on them
  2. disable the beta feature “multi-instance releases: public beta”

And with that, the apps we’d defined for other “spaces” started showing up for the new space.

Thanks @Darren !

1 Like