Agent Scripting API 409 on Update with Multi-Org Tenant

Quick question, has anyone seen this weird error? with the /v2/scripts endpoint when updating an existing script via our AppFoundry integration.

HTTP 409 Conflict: Script is currently in use by an active Architect flow

We have verified no active flows reference this script ID, yet the update fails. Is there a caching delay for script dependency checks in the platform API, or do we need to explicitly release locks before pushing updates?