Files cannot be uploaded: storage is not configured, the file is too big or empty, or it went missing

Question 1

Why do I see "File storage is not configured yet. Files can be attached once the object-storage settings are in place."?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 2

Why do I see "File storage is not configured yet, so files cannot be attached for now. Dates are recorded as usual."?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 3

Why do I see "Uploads need the object store; set S3_* in the environment"?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 4

Why do I see "Save the letterhead first, then upload a logo."?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 5

Why do I see "The file is empty"?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 6

Why do I see "Files are limited to <n> MB"?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 7

Why do I see "The file is larger than the upload limit."?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 8

Why do I see "The uploaded file is no longer in the store"?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 9

Why do I see "The files could not be uploaded."?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 10

Why do I see """ completed, but files were not uploaded: . Add them from the stage's Files."?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 11

Why do I see " files were not uploaded: "?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Question 12

Why do I see "An uploaded document has no rendered HTML; download the file"?

Accepted Answer

Generated documents are rendered from templates and can always be produced again, but an uploaded
file exists only as the bytes you gave the app. Those bytes are kept in an object store (a bucket)
that belongs to the installation, and the app has no setting for it: the store's address, bucket
and keys are part of the server set-up done by whoever runs the installation. While that is
missing, the app refuses to accept a file it could not keep, rather than pretend. Dates, statuses
and records that go with the upload (a stage's completion date, an offer's signed date) are still
saved, so the paperwork can be attached later.

The si 1. Ask the person who runs your installation to configure the object store (or to check it).
   There is nothing to set inside the app. Meanwhile keep the files where they are; the records
   that need them are already saved.
2. Once storage is set up, attach what was skipped:
   - a stage's files with the Attach file icon on the stage's row on
     Construction Stages (the Edit
     permission on Construction Stages; in the default roles the Administrator, the
     Project Manager, the Compliance Officer and the Site Engineer);
   - a logo with Upload logo on the saved letterhead (the Edit permission on Document
     Templates);
   - an allottee's papers or a signed offer copy with Upload on the
     Allottee page (the Create permission on
     Generated Documents).
   - to mark an offer signed before storage is ready, press Cancel in Mark the offer
     signed, open it again and press Mark signed without choosing a file; upload the copy
     later from the allottee page.
3. Too big: compress or split the file (scan at a lower resolution, export the PDF at a smaller
   si

Files cannot be uploaded: storage is not configured, the file is too big or empty, or it went missing

Messages this explains

Files cannot be uploaded: storage is not configured, the file is too big or empty, or it went missing

What you see

Why it happens

How to fix it

Related