@camunda8/orchestration-cluster-api 9.1.4 → 9.1.5

package/dist/fp/index.d.cts

@@ -1,4 +1,4 @@
-export { d as CamundaFpClient, AB as DomainError, AC as DomainErrorTag, E as Either, AE as FnKeys, AF as Fpify, AH as HttpError, AI as Left, AJ as Right, AL as TaskEither, AA as classifyDomainError, e as createCamundaFpClient, AD as eventuallyTE, AG as foldDomainError, i as isLeft, f as isRight, AK as retryTE, AM as withTimeoutTE } from '../index-DKqh2mnN.cjs';
+export { d as CamundaFpClient, AB as DomainError, AC as DomainErrorTag, E as Either, AE as FnKeys, AF as Fpify, AH as HttpError, AI as Left, AJ as Right, AL as TaskEither, AA as classifyDomainError, e as createCamundaFpClient, AD as eventuallyTE, AG as foldDomainError, i as isLeft, f as isRight, AK as retryTE, AM as withTimeoutTE } from '../index-MCY6xbCc.cjs';
 import 'zod';
 import '../logger-D-p21VHo.cjs';
 import 'node:worker_threads';

package/dist/fp/index.d.ts

@@ -1,4 +1,4 @@
-export { d as CamundaFpClient, AB as DomainError, AC as DomainErrorTag, E as Either, AE as FnKeys, AF as Fpify, AH as HttpError, AI as Left, AJ as Right, AL as TaskEither, AA as classifyDomainError, e as createCamundaFpClient, AD as eventuallyTE, AG as foldDomainError, i as isLeft, f as isRight, AK as retryTE, AM as withTimeoutTE } from '../index-CJBSKpFZ.js';
+export { d as CamundaFpClient, AB as DomainError, AC as DomainErrorTag, E as Either, AE as FnKeys, AF as Fpify, AH as HttpError, AI as Left, AJ as Right, AL as TaskEither, AA as classifyDomainError, e as createCamundaFpClient, AD as eventuallyTE, AG as foldDomainError, i as isLeft, f as isRight, AK as retryTE, AM as withTimeoutTE } from '../index-BIErHz2h.js';
 import 'zod';
 import '../logger-D-p21VHo.js';
 import 'node:worker_threads';

package/dist/fp/index.js

@@ -7,7 +7,7 @@ import {
   isRight,
   retryTE,
   withTimeoutTE
-} from "../chunk-4NRTES5E.js";
+} from "../chunk-JV6P7LF3.js";
 import "../chunk-KQ4UL2WX.js";
 import "../chunk-DGUM43GV.js";
 export {

package/dist/{index-CJBSKpFZ.d.ts → index-BIErHz2h.d.ts}

@@ -3007,13 +3007,15 @@ type DeploymentResourceResult = {
 type DeleteResourceRequest = {
     operationReference?: OperationReference;
     /**
-     * Indicates if the historic data of a process resource should be deleted via a
-     * batch operation asynchronously.
-     *
-     * This flag is only effective for process resources. For other resource types
-     * (decisions, forms, generic resources), this flag is ignored and no history
-     * will be deleted. In those cases, the `batchOperation` field in the response
-     * will not be populated.
+     * Indicates if the historic data associated with the resource should also be deleted
+     * asynchronously.
+     *
+     * This flag is effective for process definitions and decision requirements definitions.
+     * For other resource types (forms, generic resources) it is ignored and no history is
+     * deleted. For a decision requirements definition the `batchOperation` field in the
+     * response carries the created batch operation. For a process definition the history is
+     * deleted as part of the definition's draining/deletion lifecycle and no batch operation is
+     * returned.
      *
      */
     deleteHistory?: boolean;
@@ -3026,9 +3028,14 @@ type DeleteResourceResponse = {
     /**
      * The batch operation created for asynchronously deleting the historic data.
      *
-     * This field is only populated when the request `deleteHistory` is set to `true` and the resource
-     * is a process definition. For other resource types (decisions, forms, generic resources),
-     * this field will be `null`.
+     * Populated when `deleteHistory` is `true` and either the resource is a decision
+     * requirements definition, or the resource is a process definition that is already fully
+     * deleted from the runtime state (its history is purged directly by a batch operation).
+     *
+     * For a process definition that still exists in the runtime state, deletion first drains
+     * the definition and its history is removed asynchronously as part of that lifecycle, so no
+     * batch operation is returned and this field is `null`. It is also `null` for forms and
+     * generic resources.
      *
      */
     batchOperation: BatchOperationCreatedResult | null;
@@ -6296,12 +6303,14 @@ type ProcessDefinitionFilter = {
     /**
      * Filter by the process definition's state.
      * When not set, process definitions in any state are returned.
-     * Set to `ACTIVE` to exclude deleted definitions (recommended for most use cases).
+     * Set to `ACTIVE` to exclude draining and deleted definitions (recommended for most use cases).
+     * Set to `DRAINING` to return only definitions that are being deleted but still have
+     * active process instances draining.
      * Set to `DELETED` to return only definitions that have been deleted but are still
      * retained in secondary storage.
      *
      */
-    state?: 'ACTIVE' | 'DELETED';
+    state?: 'ACTIVE' | 'DRAINING' | 'DELETED';
 };
 type ProcessDefinitionSearchQueryResult = SearchQueryResponse & {
     /**
@@ -6344,8 +6353,11 @@ type ProcessDefinitionResult = {
     hasStartForm: boolean;
     /**
      * The state of this process definition.
+     * `DRAINING` indicates the definition is being deleted but still has active process
+     * instances draining before it is removed.
+     *
      */
-    state: 'ACTIVE' | 'DELETED';
+    state: 'ACTIVE' | 'DRAINING' | 'DELETED';
 };
 /**
  * Process definition element statistics request.
@@ -6563,7 +6575,7 @@ type ProcessInstanceCreationInstructionById = {
      */
     processDefinitionId: ProcessDefinitionId;
     /**
-     * The version of the process. By default, the latest version of the process is used.
+     * The version of the process. If omitted, the latest active version is used.
      *
      */
     processDefinitionVersion?: number;
@@ -16672,7 +16684,7 @@ declare const createDeployment: <ThrowOnError extends boolean = true>(options: O
  *
  * Upload a document to the Camunda 8 cluster.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
  *
  */
 declare const createDocument: <ThrowOnError extends boolean = true>(options: Options<CreateDocumentData, ThrowOnError>) => RequestResult<CreateDocumentResponses, CreateDocumentErrors, ThrowOnError, "fields">;
@@ -16693,7 +16705,7 @@ declare const createDocument: <ThrowOnError extends boolean = true>(options: Opt
  * each of which contains the file name of the document that failed to upload and the reason for the failure.
  * The client can choose to retry the whole batch or individual documents based on the response.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
  *
  */
 declare const createDocuments: <ThrowOnError extends boolean = true>(options: Options<CreateDocumentsData, ThrowOnError>) => RequestResult<CreateDocumentsResponses, CreateDocumentsErrors, ThrowOnError, "fields">;
@@ -16702,7 +16714,7 @@ declare const createDocuments: <ThrowOnError extends boolean = true>(options: Op
  *
  * Delete a document from the Camunda 8 cluster.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
  *
  */
 declare const deleteDocument: <ThrowOnError extends boolean = true>(options: Options<DeleteDocumentData, ThrowOnError>) => RequestResult<DeleteDocumentResponses, DeleteDocumentErrors, ThrowOnError, "fields">;
@@ -16711,7 +16723,7 @@ declare const deleteDocument: <ThrowOnError extends boolean = true>(options: Opt
  *
  * Download a document from the Camunda 8 cluster.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
  *
  */
 declare const getDocument: <ThrowOnError extends boolean = true>(options: Options<GetDocumentData, ThrowOnError>) => RequestResult<GetDocumentResponses, GetDocumentErrors, ThrowOnError, "fields">;
@@ -16720,7 +16732,7 @@ declare const getDocument: <ThrowOnError extends boolean = true>(options: Option
  *
  * Create a link to a document in the Camunda 8 cluster.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP
  *
  */
 declare const createDocumentLink: <ThrowOnError extends boolean = true>(options: Options<CreateDocumentLinkData, ThrowOnError>) => RequestResult<CreateDocumentLinkResponses, CreateDocumentLinkErrors, ThrowOnError, "fields">;
@@ -17148,6 +17160,8 @@ declare const getProcessDefinitionInstanceVersionStatistics: <ThrowOnError exten
  * Creates and starts an instance of the specified process.
  * The process definition to use to create the instance can be specified either using its unique key
  * (as returned by Deploy resources), or using the BPMN process id and a version.
+ * If only the process definition id is given, the latest ACTIVE version is used.
+ * If no ACTIVE version exists, the request is rejected as not found.
  *
  * Waits for the completion of the process instance before returning a result
  * when awaitCompletion is enabled.
@@ -17323,10 +17337,18 @@ declare const getResourceContent: <ThrowOnError extends boolean = true>(options:
  *
  * By default, only the resource itself is deleted from the runtime state. To also delete the
  * historic data associated with a resource, set the `deleteHistory` flag in the request body
- * to `true`. The historic data is deleted asynchronously via a batch operation. The details of
- * the created batch operation are included in the response. Note that history deletion is only
- * supported for process resources; for other resource types this flag is ignored and no history
- * will be deleted.
+ * to `true`. History deletion is supported for process definitions and decision requirements
+ * definitions; for other resource types (forms, generic resources) the flag is ignored and no
+ * history is deleted.
+ *
+ * The two supported types differ in how the history is removed. For a decision requirements
+ * definition the history is deleted asynchronously via a batch operation whose details are
+ * returned in the `batchOperation` field of the response. For a process definition that still
+ * exists in the runtime state, the definition first drains its running instances and its
+ * history is deleted asynchronously once the definition is fully removed cluster-wide; no batch
+ * operation is returned in the response. If the process definition has already been removed
+ * from the runtime state and the deletion is later re-triggered with `deleteHistory` set to
+ * `true`, a batch operation is created immediately and returned in the `batchOperation` field.
  */
 declare const deleteResource: <ThrowOnError extends boolean = true>(options: Options<DeleteResourceData, ThrowOnError>) => RequestResult<DeleteResourceResponses, DeleteResourceErrors, ThrowOnError, "fields">;
 /**
@@ -17814,6 +17836,18 @@ interface JobWorkerConfig<In extends z.ZodTypeAny = any, Out extends z.ZodTypeAn
     customHeadersSchema?: Headers;
     /** Backoff between polls - default 1ms */
     pollIntervalMs?: number;
+    /**
+     * Floor (ms) of the exponential backoff applied between *failed* activation
+     * requests (connection refused, connect timeout, broker restart, LAN blip …).
+     * The first retry waits ≈ this/2–this ms; subsequent consecutive failures
+     * double the window up to {@link pollBackoffMaxMs}, with jitter, and reset to
+     * zero on the first successful poll. Default `1000`. Set to `0` to disable backoff (failed polls then fall back to {@link pollIntervalMs} rather than retrying immediately).
+     */
+    pollBackoffMinMs?: number;
+    /**
+     * Ceiling (ms) of the between-failed-poll exponential backoff. Default `30000`.
+     */
+    pollBackoffMaxMs?: number;
     jobHandler: (job: Job<In, Headers>) => Promise<JobActionReceipt> | JobActionReceipt;
     /** Immediately start polling for work - default `true` */
     autoStart?: boolean;
@@ -17864,6 +17898,8 @@ declare class JobWorker {
     private _stopped;
     private _pollTimer;
     private _inFlightActivation;
+    /** Consecutive failed activation requests; drives the retry backoff, reset on success. */
+    private _consecutiveActivationErrors;
     private _log;
     constructor(client: CamundaClient, cfg: JobWorkerConfig);
     get name(): string;
@@ -17980,6 +18016,18 @@ interface ThreadedJobWorkerConfig<In extends z.ZodTypeAny = any, Out extends z.Z
     customHeadersSchema?: Headers;
     /** Backoff between polls - default 1ms */
     pollIntervalMs?: number;
+    /**
+     * Floor (ms) of the exponential backoff applied between *failed* activation
+     * requests (connection refused, connect timeout, broker restart, LAN blip …).
+     * The first retry waits ≈ this/2–this ms; subsequent consecutive failures
+     * double the window up to {@link pollBackoffMaxMs}, with jitter, and reset to
+     * zero on the first successful poll. Default `1000`. Set to `0` to disable backoff (failed polls then fall back to {@link pollIntervalMs} rather than retrying immediately).
+     */
+    pollBackoffMinMs?: number;
+    /**
+     * Ceiling (ms) of the between-failed-poll exponential backoff. Default `30000`.
+     */
+    pollBackoffMaxMs?: number;
     /** Immediately start polling for work - default `true` */
     autoStart?: boolean;
     /** Concurrency limit — default `10`. Overridden by CAMUNDA_WORKER_MAX_CONCURRENT_JOBS env var. */
@@ -18036,6 +18084,8 @@ declare class ThreadedJobWorker {
     private _stopped;
     private _pollTimer;
     private _inFlightActivation;
+    /** Consecutive failed activation requests; drives the retry backoff, reset on success. */
+    private _consecutiveActivationErrors;
     private _log;
     private _jobQueue;
     constructor(client: CamundaClient, pool: ThreadPool, cfg: ThreadedJobWorkerConfig);
@@ -20951,7 +21001,7 @@ declare class CamundaClient {
      *
      * Upload a document to the Camunda 8 cluster.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
      *
       *
      * @example Upload a document
@@ -20978,7 +21028,7 @@ declare class CamundaClient {
      *
      * Create a link to a document in the Camunda 8 cluster.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP
      *
       *
      * @example Create a document link
@@ -21015,7 +21065,7 @@ declare class CamundaClient {
      * each of which contains the file name of the document that failed to upload and the reason for the failure.
      * The client can choose to retry the whole batch or individual documents based on the response.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
      *
       *
      * @example Upload multiple documents
@@ -21164,6 +21214,8 @@ declare class CamundaClient {
      * Creates and starts an instance of the specified process.
      * The process definition to use to create the instance can be specified either using its unique key
      * (as returned by Deploy resources), or using the BPMN process id and a version.
+     * If only the process definition id is given, the latest ACTIVE version is used.
+     * If no ACTIVE version exists, the request is rejected as not found.
      *
      * Waits for the completion of the process instance before returning a result
      * when awaitCompletion is enabled.
@@ -21359,7 +21411,7 @@ declare class CamundaClient {
      *
      * Delete a document from the Camunda 8 cluster.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
      *
       *
      * @example Delete a document
@@ -21502,10 +21554,18 @@ declare class CamundaClient {
      *
      * By default, only the resource itself is deleted from the runtime state. To also delete the
      * historic data associated with a resource, set the `deleteHistory` flag in the request body
-     * to `true`. The historic data is deleted asynchronously via a batch operation. The details of
-     * the created batch operation are included in the response. Note that history deletion is only
-     * supported for process resources; for other resource types this flag is ignored and no history
-     * will be deleted.
+     * to `true`. History deletion is supported for process definitions and decision requirements
+     * definitions; for other resource types (forms, generic resources) the flag is ignored and no
+     * history is deleted.
+     *
+     * The two supported types differ in how the history is removed. For a decision requirements
+     * definition the history is deleted asynchronously via a batch operation whose details are
+     * returned in the `batchOperation` field of the response. For a process definition that still
+     * exists in the runtime state, the definition first drains its running instances and its
+     * history is deleted asynchronously once the definition is fully removed cluster-wide; no batch
+     * operation is returned in the response. If the process definition has already been removed
+     * from the runtime state and the deletion is later re-triggered with `deleteHistory` set to
+     * `true`, a batch operation is created immediately and returned in the `batchOperation` field.
       *
      * @example Delete a resource
      * ```ts
@@ -21917,7 +21977,7 @@ declare class CamundaClient {
      *
      * Download a document from the Camunda 8 cluster.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
      *
       *
      * @example Download a document

package/dist/{index-DKqh2mnN.d.cts → index-MCY6xbCc.d.cts}

@@ -3007,13 +3007,15 @@ type DeploymentResourceResult = {
 type DeleteResourceRequest = {
     operationReference?: OperationReference;
     /**
-     * Indicates if the historic data of a process resource should be deleted via a
-     * batch operation asynchronously.
-     *
-     * This flag is only effective for process resources. For other resource types
-     * (decisions, forms, generic resources), this flag is ignored and no history
-     * will be deleted. In those cases, the `batchOperation` field in the response
-     * will not be populated.
+     * Indicates if the historic data associated with the resource should also be deleted
+     * asynchronously.
+     *
+     * This flag is effective for process definitions and decision requirements definitions.
+     * For other resource types (forms, generic resources) it is ignored and no history is
+     * deleted. For a decision requirements definition the `batchOperation` field in the
+     * response carries the created batch operation. For a process definition the history is
+     * deleted as part of the definition's draining/deletion lifecycle and no batch operation is
+     * returned.
      *
      */
     deleteHistory?: boolean;
@@ -3026,9 +3028,14 @@ type DeleteResourceResponse = {
     /**
      * The batch operation created for asynchronously deleting the historic data.
      *
-     * This field is only populated when the request `deleteHistory` is set to `true` and the resource
-     * is a process definition. For other resource types (decisions, forms, generic resources),
-     * this field will be `null`.
+     * Populated when `deleteHistory` is `true` and either the resource is a decision
+     * requirements definition, or the resource is a process definition that is already fully
+     * deleted from the runtime state (its history is purged directly by a batch operation).
+     *
+     * For a process definition that still exists in the runtime state, deletion first drains
+     * the definition and its history is removed asynchronously as part of that lifecycle, so no
+     * batch operation is returned and this field is `null`. It is also `null` for forms and
+     * generic resources.
      *
      */
     batchOperation: BatchOperationCreatedResult | null;
@@ -6296,12 +6303,14 @@ type ProcessDefinitionFilter = {
     /**
      * Filter by the process definition's state.
      * When not set, process definitions in any state are returned.
-     * Set to `ACTIVE` to exclude deleted definitions (recommended for most use cases).
+     * Set to `ACTIVE` to exclude draining and deleted definitions (recommended for most use cases).
+     * Set to `DRAINING` to return only definitions that are being deleted but still have
+     * active process instances draining.
      * Set to `DELETED` to return only definitions that have been deleted but are still
      * retained in secondary storage.
      *
      */
-    state?: 'ACTIVE' | 'DELETED';
+    state?: 'ACTIVE' | 'DRAINING' | 'DELETED';
 };
 type ProcessDefinitionSearchQueryResult = SearchQueryResponse & {
     /**
@@ -6344,8 +6353,11 @@ type ProcessDefinitionResult = {
     hasStartForm: boolean;
     /**
      * The state of this process definition.
+     * `DRAINING` indicates the definition is being deleted but still has active process
+     * instances draining before it is removed.
+     *
      */
-    state: 'ACTIVE' | 'DELETED';
+    state: 'ACTIVE' | 'DRAINING' | 'DELETED';
 };
 /**
  * Process definition element statistics request.
@@ -6563,7 +6575,7 @@ type ProcessInstanceCreationInstructionById = {
      */
     processDefinitionId: ProcessDefinitionId;
     /**
-     * The version of the process. By default, the latest version of the process is used.
+     * The version of the process. If omitted, the latest active version is used.
      *
      */
     processDefinitionVersion?: number;
@@ -16672,7 +16684,7 @@ declare const createDeployment: <ThrowOnError extends boolean = true>(options: O
  *
  * Upload a document to the Camunda 8 cluster.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
  *
  */
 declare const createDocument: <ThrowOnError extends boolean = true>(options: Options<CreateDocumentData, ThrowOnError>) => RequestResult<CreateDocumentResponses, CreateDocumentErrors, ThrowOnError, "fields">;
@@ -16693,7 +16705,7 @@ declare const createDocument: <ThrowOnError extends boolean = true>(options: Opt
  * each of which contains the file name of the document that failed to upload and the reason for the failure.
  * The client can choose to retry the whole batch or individual documents based on the response.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
  *
  */
 declare const createDocuments: <ThrowOnError extends boolean = true>(options: Options<CreateDocumentsData, ThrowOnError>) => RequestResult<CreateDocumentsResponses, CreateDocumentsErrors, ThrowOnError, "fields">;
@@ -16702,7 +16714,7 @@ declare const createDocuments: <ThrowOnError extends boolean = true>(options: Op
  *
  * Delete a document from the Camunda 8 cluster.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
  *
  */
 declare const deleteDocument: <ThrowOnError extends boolean = true>(options: Options<DeleteDocumentData, ThrowOnError>) => RequestResult<DeleteDocumentResponses, DeleteDocumentErrors, ThrowOnError, "fields">;
@@ -16711,7 +16723,7 @@ declare const deleteDocument: <ThrowOnError extends boolean = true>(options: Opt
  *
  * Download a document from the Camunda 8 cluster.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
  *
  */
 declare const getDocument: <ThrowOnError extends boolean = true>(options: Options<GetDocumentData, ThrowOnError>) => RequestResult<GetDocumentResponses, GetDocumentErrors, ThrowOnError, "fields">;
@@ -16720,7 +16732,7 @@ declare const getDocument: <ThrowOnError extends boolean = true>(options: Option
  *
  * Create a link to a document in the Camunda 8 cluster.
  *
- * Note that this is currently supported for document stores of type: AWS, GCP
+ * Note that this is currently supported for document stores of type: AWS, Azure, GCP
  *
  */
 declare const createDocumentLink: <ThrowOnError extends boolean = true>(options: Options<CreateDocumentLinkData, ThrowOnError>) => RequestResult<CreateDocumentLinkResponses, CreateDocumentLinkErrors, ThrowOnError, "fields">;
@@ -17148,6 +17160,8 @@ declare const getProcessDefinitionInstanceVersionStatistics: <ThrowOnError exten
  * Creates and starts an instance of the specified process.
  * The process definition to use to create the instance can be specified either using its unique key
  * (as returned by Deploy resources), or using the BPMN process id and a version.
+ * If only the process definition id is given, the latest ACTIVE version is used.
+ * If no ACTIVE version exists, the request is rejected as not found.
  *
  * Waits for the completion of the process instance before returning a result
  * when awaitCompletion is enabled.
@@ -17323,10 +17337,18 @@ declare const getResourceContent: <ThrowOnError extends boolean = true>(options:
  *
  * By default, only the resource itself is deleted from the runtime state. To also delete the
  * historic data associated with a resource, set the `deleteHistory` flag in the request body
- * to `true`. The historic data is deleted asynchronously via a batch operation. The details of
- * the created batch operation are included in the response. Note that history deletion is only
- * supported for process resources; for other resource types this flag is ignored and no history
- * will be deleted.
+ * to `true`. History deletion is supported for process definitions and decision requirements
+ * definitions; for other resource types (forms, generic resources) the flag is ignored and no
+ * history is deleted.
+ *
+ * The two supported types differ in how the history is removed. For a decision requirements
+ * definition the history is deleted asynchronously via a batch operation whose details are
+ * returned in the `batchOperation` field of the response. For a process definition that still
+ * exists in the runtime state, the definition first drains its running instances and its
+ * history is deleted asynchronously once the definition is fully removed cluster-wide; no batch
+ * operation is returned in the response. If the process definition has already been removed
+ * from the runtime state and the deletion is later re-triggered with `deleteHistory` set to
+ * `true`, a batch operation is created immediately and returned in the `batchOperation` field.
  */
 declare const deleteResource: <ThrowOnError extends boolean = true>(options: Options<DeleteResourceData, ThrowOnError>) => RequestResult<DeleteResourceResponses, DeleteResourceErrors, ThrowOnError, "fields">;
 /**
@@ -17814,6 +17836,18 @@ interface JobWorkerConfig<In extends z.ZodTypeAny = any, Out extends z.ZodTypeAn
     customHeadersSchema?: Headers;
     /** Backoff between polls - default 1ms */
     pollIntervalMs?: number;
+    /**
+     * Floor (ms) of the exponential backoff applied between *failed* activation
+     * requests (connection refused, connect timeout, broker restart, LAN blip …).
+     * The first retry waits ≈ this/2–this ms; subsequent consecutive failures
+     * double the window up to {@link pollBackoffMaxMs}, with jitter, and reset to
+     * zero on the first successful poll. Default `1000`. Set to `0` to disable backoff (failed polls then fall back to {@link pollIntervalMs} rather than retrying immediately).
+     */
+    pollBackoffMinMs?: number;
+    /**
+     * Ceiling (ms) of the between-failed-poll exponential backoff. Default `30000`.
+     */
+    pollBackoffMaxMs?: number;
     jobHandler: (job: Job<In, Headers>) => Promise<JobActionReceipt> | JobActionReceipt;
     /** Immediately start polling for work - default `true` */
     autoStart?: boolean;
@@ -17864,6 +17898,8 @@ declare class JobWorker {
     private _stopped;
     private _pollTimer;
     private _inFlightActivation;
+    /** Consecutive failed activation requests; drives the retry backoff, reset on success. */
+    private _consecutiveActivationErrors;
     private _log;
     constructor(client: CamundaClient, cfg: JobWorkerConfig);
     get name(): string;
@@ -17980,6 +18016,18 @@ interface ThreadedJobWorkerConfig<In extends z.ZodTypeAny = any, Out extends z.Z
     customHeadersSchema?: Headers;
     /** Backoff between polls - default 1ms */
     pollIntervalMs?: number;
+    /**
+     * Floor (ms) of the exponential backoff applied between *failed* activation
+     * requests (connection refused, connect timeout, broker restart, LAN blip …).
+     * The first retry waits ≈ this/2–this ms; subsequent consecutive failures
+     * double the window up to {@link pollBackoffMaxMs}, with jitter, and reset to
+     * zero on the first successful poll. Default `1000`. Set to `0` to disable backoff (failed polls then fall back to {@link pollIntervalMs} rather than retrying immediately).
+     */
+    pollBackoffMinMs?: number;
+    /**
+     * Ceiling (ms) of the between-failed-poll exponential backoff. Default `30000`.
+     */
+    pollBackoffMaxMs?: number;
     /** Immediately start polling for work - default `true` */
     autoStart?: boolean;
     /** Concurrency limit — default `10`. Overridden by CAMUNDA_WORKER_MAX_CONCURRENT_JOBS env var. */
@@ -18036,6 +18084,8 @@ declare class ThreadedJobWorker {
     private _stopped;
     private _pollTimer;
     private _inFlightActivation;
+    /** Consecutive failed activation requests; drives the retry backoff, reset on success. */
+    private _consecutiveActivationErrors;
     private _log;
     private _jobQueue;
     constructor(client: CamundaClient, pool: ThreadPool, cfg: ThreadedJobWorkerConfig);
@@ -20951,7 +21001,7 @@ declare class CamundaClient {
      *
      * Upload a document to the Camunda 8 cluster.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
      *
       *
      * @example Upload a document
@@ -20978,7 +21028,7 @@ declare class CamundaClient {
      *
      * Create a link to a document in the Camunda 8 cluster.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP
      *
       *
      * @example Create a document link
@@ -21015,7 +21065,7 @@ declare class CamundaClient {
      * each of which contains the file name of the document that failed to upload and the reason for the failure.
      * The client can choose to retry the whole batch or individual documents based on the response.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
      *
       *
      * @example Upload multiple documents
@@ -21164,6 +21214,8 @@ declare class CamundaClient {
      * Creates and starts an instance of the specified process.
      * The process definition to use to create the instance can be specified either using its unique key
      * (as returned by Deploy resources), or using the BPMN process id and a version.
+     * If only the process definition id is given, the latest ACTIVE version is used.
+     * If no ACTIVE version exists, the request is rejected as not found.
      *
      * Waits for the completion of the process instance before returning a result
      * when awaitCompletion is enabled.
@@ -21359,7 +21411,7 @@ declare class CamundaClient {
      *
      * Delete a document from the Camunda 8 cluster.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
      *
       *
      * @example Delete a document
@@ -21502,10 +21554,18 @@ declare class CamundaClient {
      *
      * By default, only the resource itself is deleted from the runtime state. To also delete the
      * historic data associated with a resource, set the `deleteHistory` flag in the request body
-     * to `true`. The historic data is deleted asynchronously via a batch operation. The details of
-     * the created batch operation are included in the response. Note that history deletion is only
-     * supported for process resources; for other resource types this flag is ignored and no history
-     * will be deleted.
+     * to `true`. History deletion is supported for process definitions and decision requirements
+     * definitions; for other resource types (forms, generic resources) the flag is ignored and no
+     * history is deleted.
+     *
+     * The two supported types differ in how the history is removed. For a decision requirements
+     * definition the history is deleted asynchronously via a batch operation whose details are
+     * returned in the `batchOperation` field of the response. For a process definition that still
+     * exists in the runtime state, the definition first drains its running instances and its
+     * history is deleted asynchronously once the definition is fully removed cluster-wide; no batch
+     * operation is returned in the response. If the process definition has already been removed
+     * from the runtime state and the deletion is later re-triggered with `deleteHistory` set to
+     * `true`, a batch operation is created immediately and returned in the `batchOperation` field.
       *
      * @example Delete a resource
      * ```ts
@@ -21917,7 +21977,7 @@ declare class CamundaClient {
      *
      * Download a document from the Camunda 8 cluster.
      *
-     * Note that this is currently supported for document stores of type: AWS, GCP, in-memory (non-production), local (non-production)
+     * Note that this is currently supported for document stores of type: AWS, Azure, GCP, in-memory (non-production), local (non-production)
      *
       *
      * @example Download a document