Nuvelics documentation
Web app

SOM

Follow what your SOM bus has done in the last day, from messages received to skill results published, story by story.

If your newsroom connects Nuvelics to a SOM message bus, the SOM page shows what that connection has done: the story messages Nuvelics received from the bus, the checks it ran on them, and the results it sent back. It is one page with three tabs, Stories, Inbox and Skill runs, and it is read-only.

Who sees it

SOM appears in the sidebar, under Content, only when your organization has a SOM bus set up. That is a state of the organization, not a permission. Where it is set up, every member can read the page, Viewers included. Where it is not, the page says No SOM bus configured, and an owner or admin (the som:manage permission) sees Set up SOM bus, which leads to the SOM tab of Settings. The full list of settings tabs is in Web pages and permissions. The same admins also see Bus settings at the top of the page.

See how the bus is doing

At the top of the page:

  • A connection badge reads Connected, Connecting, Paused, Not reported yet, Status stale or Not connected.
  • Last 24 hours counts the messages Consumed off the bus, the Skill runs that followed and what was Published back, with a count of errors and, when results are waiting, the age of the Oldest pending publish. If the summary cannot load, the page says Couldn't load the activity summary.

Follow a story

The Stories tab lists the stories the bus has reported, showing open stories by default. A state filter switches between Open, Closed and All, and + Add filter adds Lifecycle phase. Each row shows:

  • The story's type (Planned, Active, Killed, Spiked, Archived or Orphan), its lifecycle phase (Developing, Ready to air, Breaking or Published), its version and its priority.
  • How many assets and snapshots it has, and when it was last updated.
  • The fact-check result: the assessment (Confirmed, Partially confirmed, Unverified or Contested) and how many claims were flagged.
  • Whether the result went back out: Published, Pending publish or Publish failed.

Choose a story to open Story lifecycle: every snapshot received for it as one block under Snapshot cycles, newest first, with the skill runs each triggered and whether their results were published. Use Load earlier snapshots for older ones, and Back to SOM activity to return.

Check what arrived

The Inbox tab lists every message consumed off the bus with its Topic, Type, Status, Story and when it was Received. A message's status is Received, Skipped (unknown), Skipped (echo) or Error; choose Show error detail on a row to read what went wrong. Filter with Status. A malformed message carries no story, so look for it here rather than under a story.

The Skill runs tab lists each check Nuvelics ran, with its Skill (Fact check or Story check), the Story, the Result, the number of Attempts and when it Started. A run is Pending publish, Completed or Failed. Filter with Status, and use Show error detail to see why a run failed.

Other ways to read this

Report a problem with this page

On this page