The conceptually consistent approach would note that a "long running polling job" is not a function. Architecturally this seems to necessitate a traditional non

The conceptually consistent approach would note that a "long running polling job" is not a function. Architecturally this seems to necessitate a traditional non-FaaS foundation of some sort. A "long running job" (aka as a process in the entirely unhip ancient history of IT) can call from this foundation to "functions" that perform a poll on a resource. I look at your scenario's stated requirements and wonder how did an asset deployment requirement morph into a operational and computational model requirement.