index.mdx

id	index
title	Error handling and troubleshooting
sidebar_label	Troubleshooting
description	Discover effective troubleshooting solutions for potential Temporal errors and edge cases with our comprehensive guides, ensuring smooth Workflow execution and error management.
toc_max_heading_level	4
keywords	error handling guide-context troubleshooting
tags	Errors Failures

Even the most reliable systems can encounter issues. Our troubleshooting guides are designed to help you quickly identify and resolve potential errors, ensuring your Temporal applications run smoothly and efficiently.

• Troubleshoot the BlobSizeLimitError: The BlobSizeLimitError happens when the size of a blob (payloads including Workflow context and each Workflow and Activity argument and return value) is too large. The maximum payload for a single request is 2 MB, and the maximum size for any Event History transaction is 4 MB.
• Troubleshoot the Deadline-Exceeded Error: The "Context: deadline exceeded" error occurs when requests to the Temporal Service by the Client or Worker cannot be completed. This can be due to network issues, timeouts, server overload, or Query errors.
• Troubleshoot the Failed Reaching Server Error: The message "Failed reaching server: last connection error" often happens due to an expired TLS certificate or during the Server startup process when Client requests reach the Server before roles are fully initialized.
• Troubleshoot missed Schedule Actions: When a Schedule does not fire at its expected time, alert on the missed catchup window metric, then narrow down to the affected Schedule with ListSchedules and DescribeSchedule.