Inflow.aiDocs

Service-task execution and recovery: current reading notes

Reviewed against fetched master 4d02326c2f on 18 November 2026.

The preserved service-task execution reference includes historical worker examples and an active-active explanation. Its reviewed upstream snapshot stays unchanged. Apply these current-source qualifications when reading it:

  • PersistentAsyncServiceTaskExecutor.execute validates the contract first. It can execute inline, return an activity-specific wait, or persist service work. Its shouldPersist explicitly leaves agent execution on the agent-run repository boundary; a missing service-run row is not proof that an activity never ran.
  • DefaultServiceTaskExecutionService.complete validates the actual output contract, records completion and resumes the original process/token/node. An activity result and the parent case's end state remain different observations. resumeOutput removes unbound executor envelope names; authored bindings and state/case result mappings determine what business work receives.
  • The six ServiceTaskRunStatus values describe durable service runs, not human tasks or case states. Claims and leases coordinate ownership of those runs. They do not establish exactly-once effects at an external destination. Reconcile the original external request before any repeat whose outcome is uncertain.
  • Studio's ReliabilitySection displays ordinary retry controls for ordinary activities, but service.integration.invoke reads the policy of its bound published Integration version instead. An absent binding or failed policy read must not be described as a confirmed no-retry policy.
  • The consultant's current lifecycle route is Live, with the case's own version and permitted Timeline, Data, Work, Activity and Time views. For a published non-lifecycle process, Monitor exposes the permitted version summary and problems, not a general run catalogue or the removed legacy run-changing controls. Do not turn the worker HTTP examples in the preserved reference into a workaround for a missing consultant action.

These notes are based on source inspection, not a new worker/provider/runtime test. For the participant-facing distinction between an unfinished draft and a completed decision, use Design and complete human tasks. For business recovery and a mapping worksheet, use Follow automatic steps and handle failures.

Try “document generation”, “integrations” or “first form”.