Spts Origin Script New -

While the update is largely stable, early adopters have reported three common issues. Here is how to solve them:

Issue 1: "Symbol not found: async_context"

Issue 2: Increased CPU usage during idle spts origin script new

Issue 3: Origin script fails on Windows Server 2016

Migration is not always automatic. While the new script is backward compatible, you should refactor your old routines to leverage the performance gains. While the update is largely stable, early adopters

Example: Old synchronous data fetch

-- Legacy Origin style
local data = SPTS.fetch("sensor_01")
SPTS.process(data)
SPTS.fetch("sensor_02")
SPTS.process(data)

This took approximately 200ms per fetch in sequence. Issue 2: Increased CPU usage during idle

Example: New asynchronous parallel fetch

-- New Origin script style
local results = await all(
    SPTS.fetch_async("sensor_01"),
    SPTS.fetch_async("sensor_02")
)
for each in results do SPTS.process(each) end

Execution time drops to ~110ms total because the fetches overlap.

The release of the SPTS Origin Script New is not the end of the road. According to the official roadmap (Q3-Q4 2026), the next iterations will include: