-
Notifications
You must be signed in to change notification settings - Fork 0
feat(server): add request-scoped timeouts for runtime job dispatch #94
Copy link
Copy link
Open
Labels
featrequest for or implementation of a new featurerequest for or implementation of a new featurenatsnvisy-nats: messaging, job queues, object storagenvisy-nats: messaging, job queues, object storageservernvisy-server: API handlers, middleware, authnvisy-server: API handlers, middleware, auth
Description
Context
Long-running redaction jobs need deadline enforcement. No timeout propagation exists for runtime job dispatch.
Requirements
- Each job dispatched to the runtime carries a request-scoped deadline
- If the runtime does not return results within the deadline, the job is marked as timed out
- The caller is notified of the timeout (HTTP response or webhook event)
- Configurable default timeout per workspace or per job type
- Timeout is propagated through NATS JetStream message headers
References
- Server docs: ARCHITECTURE.md - Job Orchestration
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
featrequest for or implementation of a new featurerequest for or implementation of a new featurenatsnvisy-nats: messaging, job queues, object storagenvisy-nats: messaging, job queues, object storageservernvisy-server: API handlers, middleware, authnvisy-server: API handlers, middleware, auth