TroubleshootingResolutions

Troubleshoot Resolutions

Recover from permission, validation, recipient, lifecycle, count, voiding, and results-report problems in Resolutions.

Last updated 2026-08-20 7 min read

Use the organization, vehicle, resolution status, and visible message to choose the narrowest recovery. Do not create a duplicate, resend results, or change membership until you know whether the original action persisted.

Create or edit is unavailable

Create new resolution, draft editing, deletion, sending, voiding, and results actions require an organization Admin with the management capability. An ordinary organization member can browse the list and supported resolution details but cannot manage the record.

Return to Venture and confirm the intended organization and vehicle.
Open Cap table → Shareholder resolutions again.
Confirm that your current organization role is Admin. The server rechecks the role when the page opens and again on each mutation.
If the role is correct but the control remains unavailable, preserve the organization, vehicle name, route, and time, then contact support.

Do not edit a generated Resolutions URL or ask another user to send from a copied page.

The form says Fix the highlighted fields

Review the first step from the top:

Resolution title is required even for Save as draft.
Voting deadline must be a future UTC date. For a reopened saved draft, actively choose a new future date if the old one has passed; Submit does not reliably revalidate an unchanged stale deadline.
Preamble is required and accepts at most 10,000 characters.
At least one Voting matter is required, and each matter accepts at most 5,000 characters.
A document must use .pdf, .doc, .docx, .odt, .jpg, .jpeg, .png, .webp, or .heic and be no larger than 250 MB (250,000,000 bytes).
Add no more than 20 resolution documents in one upload batch. This is the current queue limit, not a verified lifetime cap across saved batches.

Correct every highlighted value, then select Continue once. If Could not save the draft persists, keep the page open, record the visible message and time, and contact support before rebuilding the draft.

Recipients are missing, empty, or duplicated

The preview includes only accounts with a closed investment and only members of their default signatory group.

If No records found. appears, do not select Submit. Verify the investment state and the account’s default signatory group first.
If a person is missing, confirm that the person belongs to the default signatory group, not merely another account group.
If feeder investors are missing, review Feeder funds. A feeder selection is saved immediately, so deliberately turn an incorrect toggle off rather than expecting Previous to undo it.
If one account appears through both the main fund and a selected feeder fund, expect separate votes for those fund relationships. Confirm that both are intended.
Reload Preview and send immediately before submitting, then verify Investment account, Recipient name, and Email. The final action derives recipients again from current investment and default-signatory data, so coordinate with other Admins and keep that data unchanged through confirmation.

Do not add an unrelated signatory merely to make the preview non-empty.

Submit returned to the list but an email is missing

First check the Shareholder resolutions list. If the record shows Sent and has a Sent at date, do not submit a duplicate. Sending creates the voter assignments, dashboard tasks, notifications, and queued email jobs in one transaction, but queued email is not delivery proof.

Confirm the recipient’s reviewed email and task list through approved support procedures. Do not expose another investor’s address, vote, or documents while diagnosing delivery.

The wrong resolution or recipients were sent

A Sent resolution cannot be edited or returned to Draft.

Open the affected resolution immediately.
Open Resolution actions and select Void resolution.
Read the irreversible-action warning, confirm, and verify that the page shows Voided.
Treat unintended recipients as a possible disclosure of sensitive governance material. Voiding does not recall messages or guarantee that their existing document access was removed; follow your approved incident process and contact support through an approved private channel.
Correct the investment, feeder, or default-signatory data.
Create and review a new replacement resolution. Do not reuse the old record as proof that the replacement audience is correct.

If voiding fails, stop and contact support. Do not attempt to compensate by changing identifiers or repeatedly submitting another resolution.

Delete or void fails

Delete applies only to a Draft in the current vehicle. Void resolution applies only to Sent. A stale page can show an action after another administrator changed the status.

For Could not delete the resolution, refresh the list and confirm the status and vehicle. If the draft was already deleted, recreate it and re-upload the approved documents; deletion cannot be undone.
For Could not void title, refresh the detail page. A Voided or Closed resolution cannot be voided again.
If the record is still Sent and you are still an Admin, preserve the visible message and contact support. Do not treat membership removal as an equivalent revocation.

A removed signatory may still have an old assignment

Removing a signatory from an investment account is not currently a sufficient standalone revocation for an already-sent resolution.

Have an organization Admin open the sent record and select Void resolution.
Confirm Voided before making any replacement.
Correct the account’s default signatory group.
Create a new replacement resolution and verify its Recipients preview.
Contact support if the old resolution cannot be voided or any old task remains actionable.

Do not ask the removed signatory to test an old link or share its identifier in an unapproved channel.

The deadline passed but the status is still Sent

The deadline remains open through 23:59:59 UTC on the selected date. Expiration begins on the following UTC date, and a daily process closes expired sent resolutions.

Wait for that daily close cycle before creating results. If the record remains Sent after the following cycle, preserve the title, short ID, deadline, visible status, and observation time, then contact support. Do not upload results or try to force the state through a URL.

Votes submitted does not match the final response count

Votes submitted counts vote rows with answers recorded, so it can include Pending signatures. One account may have separate main-fund and feeder-fund rows. Response summary includes only fully Submitted votes and shows the raw Yes, No, and Abstain counts.

Open Votes by account and reconcile each account status. Do not use the broader Votes submitted value as final quorum or as evidence that every signatory finished.

Results upload or sending fails

Results are available only after the resolution is Closed.

Before sending, reload the detail page, reopen the report, verify the current filename and content, and reconcile every stored voter assignment against the intended audience. Keep the report unchanged through confirmation. If an assignment is stale or a recipient is no longer intended, do not send and contact support; a Closed resolution cannot be voided.

Message or symptom	Recovery
Could not upload the results report	Confirm the record is Closed, add exactly one supported file no larger than 250 MB, and try once more. Preserve the message if it repeats.
Replacement report is wrong	Select Upload a different results report, choose the approved file, and select Replace document. Reopen it before sending.
Could not send the resolution results	Keep the current report in place. Check whether Results report sent to the voters on changed before retrying; contact support if the outcome is unclear.
Report is only available for closed resolutions	Return to the resolution detail and verify the state. Do not reuse a report URL from another state or vehicle.
Generated PDF says Could not generate PDF	Preserve the visible message, resolution title, short ID, and time. Do not repeatedly download or expose report inputs in a public channel.

If the page already records a results-sent date, treat a second Send resolution results as a resend. Reload and confirm the current report, filename, and stored audience before accepting the resend warning.

What to include in a support request

Include the organization slug, fund or SPV name, resolution title or short ID, current status, deadline, approximate time, route reached through the intended vehicle, and exact visible message.

Never include investor email addresses, signatures, vote answers, uploaded documents, generated reports, authentication data, or copied recipient tables in a general support message. Use only an approved private channel when support explicitly needs sensitive governance material.