Skip to main content
When Oswald’s Update Request workflow does not produce the expected result, the cause is usually a missing approval step, a tier mismatch, or a configuration where Oswald has not been enabled for Update Requests. Work through the symptoms below.
Oswald and Update Requests is in pre-general-availability beta. Some behaviour described below may differ from what is currently rolled out to your account.
Cause. Either you are not on Guardian, Oswald is not enabled for Update Requests, or the feature has not yet rolled out to your account.Fix.
  1. Check your tier in Settings → Billing. Oswald is Guardian-only.
  2. Check Settings → AI → Oswald → Available on Update Requests. Toggle on if it is off.
  3. If neither is the issue, the feature has not yet been enabled on your account. The rollout is incremental through 2026. Write to support@brandatlas.pro if you would like to be added to the next cohort.
Cause. Oswald drafts; it does not apply. The apply step requires explicit brand-owner confirmation. If you closed the request without confirming, the draft did not become a change.Fix.
  1. Reopen the Update Request from the Inbox.
  2. The draft Oswald produced should still be visible in the request’s history. Review it.
  3. Click Apply to merge the draft into the brand record. Confirm.
  4. If the draft is no longer visible (the request was closed and the draft was discarded), ask Oswald to draft again with the same prompt.
Cause. Oswald’s draft is plausible but does not match what you want, usually because:
  • The brand record has an out-of-date or contradictory entry Oswald used.
  • The team member’s request was ambiguous and Oswald picked the wrong interpretation.
  • The prompt did not give Oswald enough constraints.
Fix.
  1. Reject the draft and provide a clarification in the comments.
  2. Ask Oswald to draft again with the clarification.
  3. If the brand record itself is wrong, fix the record first; then re-ask Oswald, which will draft against the correct state.
Cause. Oswald reads what it judges relevant. Occasionally it misjudges, especially when the request crosses sections in an unexpected way.Fix.
  1. In the request, reference the relevant sections explicitly in the comments: “This affects Voice and the Spring 2026 Campaign Horizon.”
  2. Ask Oswald to redraft.
  3. Confirm the read step now includes the expected sections.
Cause. This should not happen. Oswald has no path to apply without explicit confirmation.Fix.
  1. Open the affected section’s history. Look for the change. It will be attributed to a person (the brand owner or an Editor), with a note that Oswald drafted.
  2. If the attribution shows a person, the change was approved by that person. Discuss internally.
  3. If the attribution shows Oswald alone with no human approval, this is a defect. Roll back the change immediately and write to support@brandatlas.pro and security@brandatlas.pro. This is a high-priority incident.
Cause. The prompt is too open. Oswald asks rather than guesses; if the request leaves too much undecided, the clarification chain grows.Fix.
  1. Cancel the current session.
  2. Restart with a more specific prompt. Be explicit about: the section, the change, the constraints, the intended audience.
  3. If clarification is genuinely the right response (the team member’s request is unclear), comment on the request asking the team member for the specifics, then re-engage Oswald once you have them.

​
When to escalate

For routine drafting issues, the fixes above usually resolve the symptom. Write to support when:
  • Oswald is producing nothing despite the feature appearing available.
  • A change appears applied without your approval.
  • The audit trail shows behaviour that does not match what you expect.
For suspected security or correctness issues with Oswald, security@brandatlas.pro is the right address.

Update Requests with Oswald

The workflow.

Oswald and Update Requests

The AI-side explanation.

Oswald deep dive

The detailed reference.