Trust and administration

Troubleshooting

Resolve common issues with context, tools, permissions, outputs, and workflows.

The result is too generic

Add the intended audience, source material, constraints, examples, and definition of done. Remove irrelevant context.

Audience, source, length and a definition of done turn a generic ad into a specific one.
Try this
Instead of write a job ad, type: Write a job ad for a part-time bookkeeper at a 12-person plumbing business. Audience: local candidates with small-business accounting software experience. Use the attached role-description.docx, keep it under 250 words, end with how to apply. Done means I can post it today.
What you getThe ad comes back specific to the role, length and audience, and each later change is a one-line request rather than a rewrite.

A file or source is missing

Confirm the workspace includes the source and that Oppermind has permission to read it.

Check + → Files: if the file is not listed as a chip, it was never attached.
Try this
If Oppermind says it cannot see the Q2 figures, check the attachments above the composer; if q2-actuals.xlsx is not there, attach it with the paperclip and type: Use q2-actuals.xlsx, sheet Summary, for the figures.
What you getThe file chip appears above the composer and the reply now cites values from the Summary sheet instead of asking for the numbers.

A connector cannot take an action

Check whether the connector supports the action and whether write permission or approval is required.

With read-only permission the request stops with a reason; write access has to be granted first.
Try this
When the CRM connector reads records but will not update a deal, open Settings, Connectors, and check what it is allowed to change. Then attach it from + and Connectors and type: Move the Harbour Cafe deal to Proposal Sent.
What you getWith read-only permission the request stops with an explanation; with write permission granted the change is made after any approval your workflow requires.

A skill behaves inconsistently

Tighten its trigger, inputs, decision rules, and checks. Test it against examples that previously failed.

Settings → Skills showing each skill's active state.
Open the skill in Settings → Skills and tighten its inputs and checks.
Try this
Open the meeting-notes skill in Settings, Skills, add the rule If no attendee list is present, ask for it before writing action items, save it, and re-run it on the transcript that produced wrong owners last week.
What you getOn the re-run the skill asks for the attendee list first instead of guessing, and you keep that transcript as a test case for future edits.