As per our conversation via direct message, this issue appears to be due to a timeout when saving list of changeset files to database. We have now batched, the adding of changeset files to the database to avoid this error, and improved error handling with retries. See v1.9.1.538.