Bug Fix: Fixflo Override URL Path Corrected (v0.1.94)

What happened

In releases prior to v0.1.94, the BFF handler responsible for retrieving a person's Fixflo maintenance override was constructing the wrong API URL. Specifically, the getPersonFixfloOverride() function in src/lib/letmc/features.ts built a path with the fixflo segment placed before the personID segment:

GET /{clientName}/overrides/fixflo/{personID}   ← incorrect

The AgentOS specification requires the segments in the opposite order — personID first, then fixflo:

GET /{clientName}/overrides/{personID}/fixflo   ← correct

Who was affected

Any portal user or integration relying on the Fixflo maintenance override lookup for a specific person. Calls to this endpoint would have resulted in incorrect routing, likely producing 404 or unexpected responses from the AgentOS backend.

What was fixed

The path construction inside getPersonFixfloOverride() was corrected to match the spec:

// Before (v0.1.93 and earlier)
`/${trimmedShortName}/overrides/fixflo/${trimmedPersonId}`

// After (v0.1.94)
`/${trimmedShortName}/overrides/${trimmedPersonId}/fixflo`

Action required

No configuration or integration changes are required by agency administrators or end users. The fix is applied automatically as part of the v0.1.94 deployment. Fixflo override lookups will now route correctly to the AgentOS backend.

Related

• AgentOS overrides API spec: GET /{clientName}/overrides/{personID}/fixflo
• Source file: src/lib/letmc/features.ts — getPersonFixfloOverride(clientName, personID)