Settings

Coding errors

The Coding errors tab shows where the coding sessions of the workspace you're in went wrong: how often, at which stage of a run, in which repository and application, and in which session. Use it to find an install that keeps failing, a repository that can't be cloned, or an application whose sessions often stop, and to open the sessions where it happened.

Key concepts

Error. Something that went wrong in a run of a coding session: an install that failed, a repository that couldn't be cloned, a pull request that couldn't be opened. Each error says what happened, why, and what to do, and keeps the output of the program that failed, such as the install's output.

Stopped a run. An error that ended its run, so the run failed. A session's other errors and its warnings didn't stop it: the run went on past them.

Failed run. A run that stopped on an error. Each failed run is counted once.

Stage. Where in a run the error happened: Dispatch, Runner, Workspace, Clone, Push checks, Install, Coding agent, Publish, Preview or Scan.

Period. The last 7, 30 or 90 days. Errors are kept for 90 days.

The Coding errors tab at a glance

In the sidebar, choose Settings, then Coding errors. From top to bottom, the tab shows:

  • The period and the application: 7 days, 30 days or 90 days, and All applications or one of them. Productmind remembers both for you in this workspace.
  • The summary: Errors, Failed runs, Sessions affected and Applications affected. Errors per day has a bar for each day, the errors that Stopped a run under the Other errors: point at a day to see its counts. Then Most frequent, each kind of error with how often it happened and when it last did, By stage, and By repository.
  • By application: each application's Errors, Runs stopped, Most frequent error and Last seen.
  • The errors, newest first. Each one shows a mark for how serious it was (a cross when it stopped the run, a circled exclamation mark for an error, a triangle for a warning), its title, its stage, the repository and applications it concerns, the run it happened in (such as Build), when it happened, and its session, such as SSID-12: Login fix.

With one application chosen, the summary and the errors are that application's, and By application is hidden.

Reading the errors

To see where your coding sessions went wrong

  1. In the sidebar, choose Settings, then Coding errors.
  2. Choose the period: 7 days, 30 days or 90 days.
  3. To see one application's errors, choose it in place of All applications.

The summary, By application and the list show that period's errors. When there are none, the list says No coding errors in the last 30 days., with the period you chose.

To read an error

  1. Choose the error in the list.
  2. Read what happened and what to do, and under Output, what the program printed.
  3. To copy the output, choose the copy button beside Output.
  4. To open the session the error happened in, choose its session, such as SSID-12: Login fix.
  5. To fix it in a session of its own, choose Launch a bug fix session.

The error expands, and its output shows at once. A long output shows its last lines first, and all of it once it has loaded. Expand all opens every error in the list, and Collapse all closes them. To see older errors in the period, choose Show older errors at the end of the list.

Launch a bug fix session files a bug report from the error (what happened, the hint, the output and where it happened) and opens a bug fix session for it, in planning, on the repositories and sandbox of the session the error happened in. The error then offers Open bug fix session, or Retry bug fix session if the report was filed but its session wasn't created; Retry uses the same report. The output goes into the report only if you have Logs: Read. You need Sessions: Create and Bug reports: Create, and the button is grayed out while cloud sessions are off and your Productmind agent isn't running. It is on each error of a session's Errors tab too: see To fix an error in its own session.

To see one application's errors

Each application has a Coding errors view of its own, under Insights in its menu, beside Documentation, Features and Readiness. It shows the same things for that application alone, and the workspace's managers see it: an Owner or Admin of your organization, the workspace's owner, or one of its admins.

  1. In By application, choose the application. It opens with its Coding errors view. Or open the application from Applications, and choose Coding errors in its menu.
  2. Choose the period: 7 days, 30 days or 90 days.

The view shows the application's Errors, Failed runs and Sessions affected, Errors per day, the Most frequent errors, By stage and By repository, then its errors, newest first. Its period is remembered on its own, the same for every application. To come back to every application's errors, choose Settings > Coding errors at the top of the view.

How Coding errors behaves

Every coding session of the workspace is counted. Errors from runs on Productmind's cloud and on your own machine are counted alike, and so are the errors of scans and live previews.

The workspace's numbers count each error once. In By application and on each application's own tab, an error that concerned two applications counts in each of them.

An error belongs to the applications its run worked on. When the error names its application, it counts there. Otherwise it counts for the run's applications in the error's repository, or for every application of the run. An error that concerned no application is listed as No application.

Errors in someone else's code chat are counted, not listed. A Code conversation is private to the person who started it, so its errors count in the numbers but don't appear in the list. When a period's only errors are in other people's code chats, the list says so.

What a run's own people see. Everyone who can follow a session sees its errors in the session's Errors tab. See Working in a session.

Errors are deleted after 90 days, with their output. Deleting a session deletes its errors.

Permissions

ToYou need
See Coding errorsThe Owner or Admin role
See an application's Coding errors viewTo manage the workspace (an Owner or Admin of your organization, the workspace's owner, or one of its admins), and Sessions: Read
Read an error's outputLogs: Read. Without it, you see each error's title, what happened and what to do
Choose one applicationApplications: Read

Limits

LimitValue
PeriodThe last 7, 30 or 90 days
How long errors are kept90 days
Errors recorded for one run50
An error's saved output5 MB. A longer output keeps its beginning and its end

Troubleshooting

The Coding errors tab shows a lock

Your plan doesn't include coding sessions. See Plans and limits.

An error says "The full output wasn't saved."

The error's full output is no longer in storage. Its last lines, what happened and what to do are still shown. An output that couldn't be saved when the error happened ends with (The full output couldn't be saved.) instead.

An application has no Coding errors view

Only the workspace's managers see it: an Owner or Admin of your organization, the workspace's owner, or one of its admins. If the view is locked, your plan doesn't include coding sessions.

There is no application filter

You need Applications: Read to choose an application. Without it, the tab shows every application's errors.

Last modified on