Short answer: Most loading or saving issues clear up with a refresh; if a specific save keeps failing, check for the on-screen error message and try again before contacting support.
The page won't load
Refresh the page. Most sections load fine on a second attempt.
Check you're signed in with the correct account. If your session has expired, you'll be prompted to sign in again.
Try a different browser tab or window if the section still won't open.
Note: If a section looks locked with a "Never shared" or "Only you" chip, that's expected for Financials and Vision & Leadership. Those two sections are owner-only and never delegated to teammates.
The page won't save
The portal saves automatically as you go. There's no Save button to click, so if it looks like nothing happened when you moved to the next field, that's normal.
Look for a confirmation near the field. Most fields save quietly in the background a moment after you stop typing.
In Client Journey or Team Rhythm, watch the small status chip on the meeting card. It reads "Saving...", "All changes saved", or "Couldn't save, retrying" if something went wrong.
If you see a failure message, wait a few seconds. Journey Builder retries failed saves automatically. For plain fields, a failed save shows a one-off message and reloads the latest saved version from the server, so check the field still shows what you expect.
Warning: There's no warning if you close the tab while a save is still in progress, and the portal doesn't detect when you've gone offline. If you're mid-sentence and close the tab, that last bit of typing can be lost. Navigating to another section inside the app is safe; it saves your work first.
An error appears when you submit
Read the message shown on screen. It usually points to what needs fixing, for example a file that doesn't meet the upload requirements or a required field left blank.
If it's a file upload, check the file type and size. Each upload slot only accepts specific file types, and files must be under the size limit. Rejected files show a "Rejected" chip when the page reloads.
Refresh and try the action again. Occasionally a one-off hiccup clears on retry.
If the same error keeps happening, note what you were doing and reach out for help.
A button isn't working
Refresh the page first; this resolves most unresponsive buttons.
Check whether the button is meant to be active yet. Some steps only unlock once earlier fields are filled in.
If a button still does nothing after a refresh, get in touch with support and describe exactly which button and section it was.
Tip: When you contact support about any of the above, include the section name and roughly what you were doing when it happened. It makes tracking down the cause much faster.