Skip to main content

Why is my backup empty or missing data?

Written by ProBackup

This article explains what to check when your backup shows no data, only a few MB of storage, or projects that you know are not empty.

The first backup has not finished yet

After you connect an app, ProBackup starts an initial pull of all your data. Until that pull finishes, the app shows a small storage figure and few or no records. Large workspaces can take several hours. Check back later in the day before you change anything, and do not delete the connection or your account: starting over restarts the same pull.

The connected account cannot see the data

ProBackup only backs up what the account you connected can open in the app itself. A guest, limited member or single-project account produces a nearly empty backup even though the connection is active.

  • Sign in to the connected app and check that your account is a full member or an administrator of the workspace.

  • Open the project or board that shows no data. If you cannot open it there, ProBackup cannot back it up either.

  • For private projects, either invite the backup account to them, or invite the colleague who owns them as a ProBackup user so their access is added to the backup.

Part of the app is outside your backup scope

Workspaces, bases, teamspaces and boards are selected when you connect an app, and anything created afterwards is not added automatically.

  1. On the Home page, open the app.

  2. Open the Scope tab.

  3. Include the workspaces, projects or spaces that are missing and save.

The app blocks third-party access

Some apps require an administrator to approve third-party apps before they can read anything. When this is on and ProBackup was never approved, the connection looks fine and stays empty. Check the third-party app settings in the connected app's admin console and approve ProBackup, then reconnect.

Still empty

Send us the name of the app, the email address of the connected account and one project that should contain data. We can then see whether the pull ran and what the app returned.

Did this answer your question?