Skip to content
Orbitify
Changelog

Release 2026.11.02

Every change we make that people can see, newest first. Each release is named by the day it went out.

November 2, 2026Release 2026.11.02

Changed

Orbitify checks each drone inspection first

Before, anyone who could change an inspection could run its Setup steps, find and review its findings, and findings showed as soon as they were found. Now Orbitify does every step after Upload, makes new drone inspections, and checks the findings before you see them. Until then, lists say Orbitify is checking it. Once it is shown, your administrators are told, and its findings, reports and requests open to everyone who may see them. Requests are raised only from findings that are shown. Inspections made before today count as shown. You still upload the photos. This change was not announced ahead, as it should have been.

What to do, by December 2, 2026

  1. Tell your team that Orbitify now does each drone inspection's Setup after Upload and checks its findings, and that they see the findings, reports and requests once Orbitify shows the inspection.
In plans with InspectionsLink
Fixed

Findings keep their severity in operations

Before, requests and work orders read nearly every solar finding as moderate, and raising requests from many findings at once gave them all one severity. Now a finding has one severity, set when it is checked and shown in your company's own words, and each request raised from several findings takes the worst of its own findings unless you pick one.

In plans with InspectionsLink
Improved

Turbine findings lead to work orders

Before, a turbine's page had its own incident and work order forms, and its header showed figures nobody had measured, such as Running or the wind speed. Now the turbine page has two tabs: Findings, with what happened to each finding, and Requests and work orders, for the turbine's asset. A finding opens on its own request and work order. The header shows the turbine's number, make, model, serial, rotor size and when it was last inspected.

In plans with InspectionsLink
Fixed

Inspection reports download again

Before, the solar Generate Report and wind Export buttons failed with an error. Now they make the PDF again. A solar report's findings table says what happened to each finding, in plain names, and a wind report covers one visit with only what is known about its turbines. A report of an inspection Orbitify has not shown yet is made once it is shown.

In plans with InspectionsLink
Fixed

Re-checked sites keep their panels and findings

Before, checking a solar site's panels again made every panel anew: findings lost their panel, a string could be listed twice in the asset register, and panels lost their photos. Now a re-check keeps each panel with its shape on the map, its photos and its findings, and each string is listed once.

In plans with InspectionsLink
Fixed

Finish or cancel an upload you left

Before, an upload whose browser tab had closed kept showing as uploading at 0%, with Pause, for a day. Now it says it stopped and offers to finish it or cancel it, and Cancel ends it for good.

Improved

Project maps and turbine pages open faster

Before, every project's Map tab loaded the inspection Setup tools, and opening a turbine read a thousand of your company's work orders and people. Now Setup loads only when it is opened, and a turbine reads only its own requests.

How we change Orbitify

New things and fixes go out as soon as they are ready. A change to how you already work, or one that asks something of you, is announced ahead, by this much:

Kind of changeNoticeHow you hear
A new feature, an improvement or a fixNone: announced on the dayWhat's new and this page
A change to how existing work is done: a moved screen, a renamed step, a new required field, a default switched onAt least 14 daysA notice to your administrators, and a coming change in What's new
An administrator must act; a feature is removed; where data is kept, or which AI model or region answers, changesAt least 30 days, with a date to act byA notice to your administrators by email and in the Inbox until one of them acknowledges it, and a reminder 7 days before
A change that breaks what a connected system does through the API or webhooksAt least 6 months, under a new API versionThe API changelog on the developers page, an email to whoever answers for each connection, and Deprecation and Sunset headers
A security fixNone: explained afterwardsThis page

Building on the API? See the developers page for its version and its own changelog. Developers