Partial Sync or re-indexing possible?

[xannasavin]

Bug Description
I have a large WordPress Site with a Woocommerce Shop etc.
Recently it looked like the filestate json was not correct anymore, since deployment always failed (happens from time to time).
As usual I simply deleted the file, so it could be reindexed.
However, the workflow now is always running into the timelimit and fails, since there seem to be too many files.

Is it possible to re-index in another way?
Or is it possible to exclude folders and re-include them one after another, so the index is complete again?
Not sure, if you exclude folders, if they get wiped from the index?

🎉 DeployThe job running on runner GitHub Actions 20 has exceeded the maximum execution time of 360 minutes.

🎉 DeployThe operation was canceled.

[xannasavin]

I tried to exclude the plugins folder, but for some reason it still takes it into account...
there are 36,728 files. If the workflow was canceled (manually or by timeout) there is still no ftp-deploy-sync-state.json placed, so it starts from scratch every time.
Any idea?

[SHJordan]

I actually am trying to figure out a way to do the same. Since my Laravel project is big when it comes to node modules and vendor files it would be great if there was a way to write the frp-deploy-sync.json lets say, after 10 files/folders created on the remote. Or even better, check if those folders already exist in the server before re-creating them. @SamKirkland

[garrettw]

I would like to see this too. Progressive writing to the JSON file would let us pick up where we left off if a long deployment fails partway through. Or maybe on failure, detect it and make sure to write the current progress to the JSON file before exiting.

Edit: Duplicate of #341