This reference lists possible Workflow Task errors and how to resolve them.
For other types of errors, see Temporal Failures.
Bad Cancel Timer Attributes
This error indicates that the Workflow Task failed while attempting to cancel a Timer.
Check your Timer attributes for a missing Timer Id value. Add a valid Timer Id and redeploy the code.
Bad Cancel Workflow Execution Attributes
Reset any missing attributes and redeploy the Workflow Task.
Bad Complete Workflow Execution Attributes
Reset any missing attributes. Adjust the size of your Payload if it exceeds size limits.
Bad Continue as New Attributes
Reset any missing attributes. If the payload or memo exceeded size limits, adjust the input size.
Check that the Workflow is validating search attributes after unaliasing keys.
Bad Fail Workflow Execution Attributes
Bad Modify Workflow Properties Attributes
This error indicates that the Workflow Task failed to validate attributes on a property in the Upsert Memo or in a payload. These attributes are either unset or exceeding size limits.
Reset any unset and empty atrributes. Adjust the size of the Memo or payload to fit within the system's limits.
Bad Record Marker Attributes
Enter a valid Marker name and redeploy the Task.
Bad Request Cancel Activity Attributes
This error either indicates the possibility of unset attributes for RequestCancelActivity, or an invalid History Builder state.
If you continue to see this error, review your code for nondeterministic causes.
Bad Request Cancel External Workflow Execution Attributes
This error indicates that the Workflow Task failed while trying to cancel an external Workflow. Unset or invalid attributes can cause this to occur.
Reset any missing attributes, such as Workflow Id or Run Id. Adjust any fields that exceed length limits.
If Child Workflow is set to
RequestCancel, remove one of these attributes.
A Child Workflow cannot perform both actions in the same Workflow Task.
Bad Schedule Activity Attributes
Reset any unset or empty attributes. Adjust the size of the received payload to stay within the given size limit.
Bad Search Attributes
Make sure that all attributes are defined before retrying the Task. Adjust the size of the Payload to fit within the system's size limits.
Bad Signal Input Size
This error indicates that the Payload has exceeded the Signal's available input size.
Adjust the size of the Payload, and redeploy the Workflow Task.
Bad Signal Workflow Execution Attributes
Reset any unset, missing, nil, or invalid attributes. Adjust the input to fit within the system's size limits.
Bad Start Child Execution Attributes
Adjust the input size of the attributes to fall within the system's size limits.
Make sure that Search Attribute validation is performed after unaliasing keys.
Bad Start Timer Attributes
This error indicates that the scheduled Event is missing a Timer Id.
Set a valid Timer Id and retry the Workflow Task.
Cause Bad Binary
This error indicates that the Worker deployment returned a bad binary checksum.
Cause Bad Update
This error indicates that a Workflow Execution tried to complete before receiving an Update.
This error might indicate usage of an unsupported SDK. Make sure you're using a supported SDK.
Cause Reset Workflow
If the system hasn't started a new Workflow, manually reset the Workflow.
Cause Unhandled Update
UnhandledUpdate occurs when a Workflow Update is received by the Temporal Server while a Workflow Task being processed on a Worker produces a Command that would cause the Workflow to transition to a closed state.
Temporal rejects the Workflow Task completion to guarantee that the Update is eventually handled by Workflow code and rewinds the Workflow so it can handle the pending Update.
This error can happen when the Workflow receives frequent Updates.
This error indicates that the Workflow Task has failed for an unknown reason.
If you see this error, examine your Workflow Definition.
Failover Close Command
Force Close Command
This error indicates that the Workflow Task was forced to close. A retry will be scheduled if the error is recoverable.
Pending Activities Limit Exceeded
Let the Workflow complete any current Activities before redeploying the code.
Pending Child Workflows Limit Exceeded
Wait for the system to finish any currently running Child Workflows before redeploying this Task.
Pending Request Cancel Limit Exceeded
This error indicates that the Workflow Task failed after attempting to add more cancel requests. The Workflow has reached capacity for pending requests to cancel other Workflows, and cannot accept more requests.
If you see this error, give the system time to process pending requests before retrying the Task.
Pending Signals Limit Exceeded
Wait for Signals to be processed by the Workflow before retrying the Task.
Reset Sticky Task Queue
This error indicates that the Sticky Task Queueneeds to be reset.
If you see this error, reset the Sticky Task Queue. The system will retry automatically.
Resource Exhausted Cause Concurrent Limit
This error indicates that the concurrent poller count has been exhausted.
Adjust the poller count per Worker.
Resource Exhausted Cause Persistence Limit
This error indicates that the persistence rate limit has been reached.
Resource Exhausted Cause RPS Limit
This error indicates that the Workflow has exhausted its RPS limit.
Resource Exhausted Cause System Overload
This error indicates that the system is overloaded and cannot allocate further resources to Workflow Tasks.
Resource Exhausted Cause Unspecified
This error indicates that an unknown cause is preventing resources from being allocated to further Workflow Tasks.
Schedule Activity Duplicate Id
Check your code to see if you've already specified the same Activity Id in your Workflow. Enter another Activity Id, and try running the Workflow Task again.
Start Timer Duplicate Id
This error indicates that a Timer with the given Timer Id has already started.
Try entering a different Timer Id, and retry the Workflow Task.
UnhandledCommand can happen when the Workflow is receiving a high number of Signals.
If the Workflow doesn't have enough time to handle these Signals, a RetryWorkflow Task is scheduled to handle these new Events.
To prevent this error, drain the Signal Channel with the ReceiveAsync function.
If you continue to see this error, check your logs for failing Workflow Tasks. The Workflow may have been picked up by a different Worker.