This situation is related to planned events and how Infraspeak manages their execution across Work Orders (WOs) and their scheduled counterparts. Below, we explain exactly why it happens and how to resolve it. 


Before you Start

Make sure you have:

  • Permissions to view and edit Work Orders on the platform
  • Access to the web version of Infraspeak (manual resolution is done here)
  • A clear idea of which Work Order and Planned Job are involved in the situation.


Why the Work Order remains open

  1. When a Work Order is initiated, the system automatically creates an "event" dedicated to the execution of its tasks.
  2. If you schedule that WO by creating a Planned Job out of it, the system generates a second "event" for those exact same tasks.
  3. If the WO was initiated before the Planned Job was created, closing the Planned Job Order (occurrence) via the app only closes that specific scheduled event.
  4. Because the original WO event is still considered "running" by the system, the Work Order won't close automatically and will still show as open on the web.

Tip: Whenever possible, check if a Planned Job already exists for the area or asset before manually initiating a new Work Order.

How to prevent this in the future

  1. For a Work Order to automatically close the moment its associated Planned Job Order is closed, the Planned Job must be created before anyone initiates the Work Order.
  2. This way, both events are properly linked from the start, and closing the job in the app will correctly propagate to the web version.

    Tip: Establishing with your team the practice of always creating the Planned Job first avoids most of these situations and keeps your Work Order history more consistent.


Action to take now

  1. Access the web version of Infraspeak and locate the Work Order that is still showing as open.
  2. Confirm that the associated Planned Job occurrence has indeed been closed in the app.
  3. Manually close the Work Order on the platform to fully resolve the situation, since the original WO event is still running in the background.

What happens next

Once the Work Order is manually closed on the web, both events are properly finalised and the WO will no longer appear as open. From that point on, and as long as you start creating Planned Jobs before initiating new Work Orders, the system will be able to close everything automatically, with no need for manual intervention. This small change in workflow helps keep your operations record cleaner and more reliable.