Find the symptom, try the fix, and open the linked page to apply it. Most problems are a missing connection, a plan or balance that needs attention, or a message sent from the wrong address.
Symptom to fix
| Symptom | Likely cause and fix |
|---|---|
| Para never replies to my email | The message was not sent from your recognized address, or it went to another person’s Para address. Copy your address from Channels and check its setup status. |
| Para replied that my attachments are too large | Email accepts up to 10 files totaling 20 MB per message; Slack and Teams accept up to 10 files totaling 1 GB. Send smaller batches, or upload to Projects and name the files in your request. |
| Reply arrived but files are missing | In Teams, select Allow on each file card and wait for the completed file. In other apps, check for an attachment or download link. Check the assignment in Para before requesting a resend. See the integration’s file guide for limits. |
| Automation did not notify me | It may have finished quietly (nothing worth saying), or its delivery target is not connected. Check Automations, then Channels. |
| Slack/Teams messages go nowhere | The app is not installed or your identity is not linked. Reconnect from Channels. |
| Para ignores mentions in a Slack channel | Invite the Para app to the channel and link your Slack account on Channels. If Channels shows Enable Para in channels, an administrator must choose it. Mentions from Slack Connect guests are ignored. |
| My Slack or Teams message got “Got it” or “Queued” | Para was already working. “Got it” means your message is being applied to the current task; “Queued” means it will be picked up when that task finishes. |
| “No plan yet” / Para stopped running | The organization has no plan: an administrator chooses one and adds a usage balance on Plan. Already subscribed? Check your balance, payment status, and spending limits. Para’s reply links to the Plan page. |
| Plan says Para is paused | A subscription payment didn’t go through. An administrator selects Update billing on Plan to fix the card in Stripe; Para takes new work again once the payment succeeds. |
| Usage looks wrong or empty | Costs can appear after work finishes, and “still updating” means the latest costs are not confirmed yet. Members see only their own usage. Check when usage was last confirmed and compare the same period. If it still looks wrong after an update, contact support with the assignment and amount. |
| Cannot invite / cannot change that setting | Owners and administrators manage team membership, billing, and organization app installations. Ask an administrator for help. Members can manage their own personal connections. |
| Cannot sign in | Owners and administrators must use a passkey. Use your saved passkey to sign in. If password sign-in is available for your account, use Forgot password to reset it. |
| File connector is empty / keeps loading | Allow a moment for the list to load, then refresh. Confirm you connected the right account and can open the document in the original service. Reconnect from Plugins if access has expired. |
| A plugin task fails | Check the connection on Plugins, or on Shared Para for channel requests. Reconnect if the credential expired, and confirm the account has the access the task needs. |
Where everything gets fixed
- Plan and billingPlans, seats, usage balance, top-ups, payment, invoices.
- ChannelsWork, email, Slack, Teams, AI assistants, and meetings.
- Pluginscase.dev, services, document systems, and secrets.
- TeamInvitations, roles, access groups, spend caps.
- UsageReported costs and when they last updated.
- AutomationsSchedules, prompts, delivery targets.