Hi all, We’re running into an issue with literal o...
# flyte-support
r
Hi all, We’re running into an issue with literal offloading. When offloading is enabled in Propeller but the
maxMessageSize
is still at the default, we hit a gRPC message size error. Is this expected? I thought anything beyond the limit would be offloaded automatically, but instead the error still occurs. Version used: flytekit 1.15.3 and flyte core deployment 1.15.3 settings: literal-offloading-config: enabled: true (flyte core helm) Provided if we get it offloaded. The task fails with the following error asking us to increase the maxDownloadMb _Failed to read futures protobuf file., caused by: path:abfs://flytetf/metadata/propeller/flytesnacks-development-anpsssng6ms5jjkbmqpd/n3/data/0/futures.pb: [LIMIT_EXCEEDED] limit exceeded. 38.480028mb > 10mb. You can increase the limit by setting maxDownloadMBs.","ts":"2025-08-18T194716Z"_ And on increasing the MaxDownloadMBs, we are thrown with maxMessage Size error Please note: The above error is in the case of dynamic workflow We see an other issue being raised with the same problem: https://discuss.flyte.org/t/16667891/i-m-running-into-this-error-in-an-dynamic-task-toolarge-even Could you please suggest a solution or a way forward?