Troubleshoot Meet
Recover from Meet setup, discovery, matching, contact, report, Event, and visibility problems.
Use the symptom that matches what Meet shows. Do not try to bypass visibility boundaries, and do not interpret stale scheduling text as a shipped action.
Meet asks me to sign in or choose an organization
Meet itself requires a confirmed, signed-in account and no organization context. Sign in with the intended personal account, complete confirmation if /auth/confirm opens, then return to https://meet.infra.one/.
An organization role does not unlock more Meet capability. If an app switcher asks for an organization before opening some other service, return to the account-scoped Meet entry instead of changing membership or requesting an organization-admin role.
If /app/users/onboarding opens first, the shared account profile is missing a first or last name. Complete those account fields, then return to Meet. This is shared account onboarding, not one of Meet’s three profile-setup steps.
The directory keeps returning to setup
The profile is still incomplete. Setup saves each step independently but marks the profile complete only when step 3 succeeds.
- Reopen
/setup; it starts at step 1. Select or confirm GP, LP, or Other. - Select Continue to reach step 2, then supply or confirm the required profile details, including Full name (required) and Company/Organization (required).
- Select Continue to reach Select interests.
- Select at least three interests in total and choose Continue.
The success state is Completed the profile followed by the Meet directory. Reloading setup always returns to step 1; it does not mean the saved later-step data was deleted.
Step 2 does not continue
Check each enforced boundary:
- Full name (required) and Company/Organization (required) must have values.
- Full name accepts at most 160 characters.
- Bio accepts at most 1,000 characters.
- LinkedIn URL, when present, must be a valid URL on
linkedin.com. - A photo must be JPG, JPEG, PNG, WEBP, or GIF and no larger than 25 MB (25,000,000 bytes).
- Step 2 accepts one photo upload entry per submission. Remove any extra queued file before retrying.
The avatar and profile changes save in one step-2 transaction. If either part fails, correct the error and submit the step again rather than assuming the text fields were saved.
Changing Full name here updates the Meet public-profile name, not the signed-in account’s name. A saved photo updates the account’s shared avatar rather than a Meet-only image.
Step 3 says to select more interests
Meet counts selections across Asset Classes, Investment Focus, Strategies, and LP Type. The combined total must be at least three. The displayed 3–8 recommendation is guidance; there is no enforced maximum of eight.
Interest toggles are local to the current setup session until you select Continue. If the browser was closed first, select the interests again and submit the step.
No profiles match my search or filters
Name search is case-insensitive, and all active filters narrow the same completed-profile pool.
- Clear Search by name….
- Remove filters one at a time.
- Check Top picks for you before expanding a narrower section.
- For an Event filter, confirm the Event is published and the expected person has accepted attendance.
Meet never includes your own profile. It also excludes incomplete profiles, deleted accounts, and accounts with a block in either direction. Search and filters cannot override those rules.
The match score looks lower or higher than expected
Meet does not count every selected tag as one flat pool. It calculates overlap separately for four categories, excludes only categories empty on both profiles, then weights each comparable category equally. One sparse category can therefore affect the average as much as one category with many selections.
Review Shared interests and Other interests in the profile panel. If none of the four categories is comparable, the score is 0.
I cannot request contact
First inspect the button state:
- Waiting for acceptance means a pending direct chat already exists. Continue with that Messenger relationship instead of creating another. The requester can write while it is pending; the receiver must accept before writing.
- Send message means the relationship is accepted. Open the existing Messenger chat.
- Request to contact means no active or pending relationship is visible to Meet. Selecting it creates or resets one pending direct chat.
A block in either direction rejects the request and new direct messages. Self-requests, duplicate pending requests, and already accepted relationships are also rejected by the contact contract; Meet can surface a generic Could not send the contact request error. Meet has no block control, so resolve the relationship or block state in the account and Messenger controls rather than repeatedly submitting Meet.
An existing direct room can move from the normal Messenger list to Blocked; shared group-room messages remain. After unblocking, discovery and direct contact return only when the profiles and relationship meet every other eligibility rule.
A profile or Event association looks more visible than expected
Two tracked product issues affect how visibility should be interpreted:
- IO-11433 covers inconsistent profile visibility across Meet surfaces. If a profile appears unexpectedly, close it, do not share it onward, and contact support.
- IO-11434 covers an Event-association visibility inconsistency. Treat an unexpected association as private, do not share it onward, and contact support.
Blocks still remove both accounts from ordinary Meet discovery and prevent contact-request creation. These follow-ups do not authorize bypassing that behavior.
An Event attendee list has no Meet cards
The Event must enable Show Meet profiles to attendees?, and its guest-list rule must allow the current signed-in viewer to see attendees. The viewer also needs a completed Meet profile to receive the card layout. Without one, the Event can show Create profile when other accepted attendees have completed Meet profiles.
The Event guest list intentionally omits match percentages. Use the Meet directory for match scores and filtering.
An Event Meet invitation looks wrong
The invitation email uses See who else is coming to {event} and sends Create your profile directly to Meet setup. Complete the same three profile steps documented in Set up your Meet profile. A completed profile makes the Event attendee-administration value On Meet even when an older invitation time exists.
The controls that send or resend this email belong to Events administration, not the account-scoped Meet workspace. If Events reports an invitation error, an unchanged time does not prove no email was sent; confirm with the recipient before retrying to avoid a duplicate. For invitation controls, status labels, delivery failures, and resend behavior, use Troubleshoot Events. An organization role does not change ordinary Meet access, while a personal Meet profile does not grant permission to manage an Event.
Report profile does not submit
Choose one value under Why are you reporting this?; the description is optional. If no reason is selected, Meet reports Select a reason. A storage or validation failure reports Could not submit report and leaves the modal available for correction or retry.
A successful report says Submitted the report. It does not itself block the profile or change the Messenger relationship.
Meet mentions scheduling or joining
This is stale product copy tracked by IO-11438. Meet currently exposes profile setup, discovery, contact requests, reporting, Event profile links, and a Messenger handoff. It has no Meet scheduling or joining route, control, or lifecycle. Do not promise or document a scheduling outcome until that product capability ships.