New RunLLM response generated: >>>*# Question* I have a map task with cardinality 3000. It works fine, until one of the map tasks change status. The propeller then runs into an issue recording the task event. It gives a 'Request Entity Too Large' error when it tries to record a task event: # Answer The issue you're encountering is likely due to the size of the task event payload exceeding the maximum allowed size in FlytePropeller. This can happen when dealing with large fan-out tasks like map tasks with high cardinality. According to GitHub Issue #1613, large error messages or status updates can cause FlytePropeller to fail when the message size exceeds the gRPC limit. This issue is particularly prevalent in workflows with extensive fan-outs, such as your map task with 3000 elements. Would you like more details on potential workarounds or solutions? Sources: - GitHub Issue #1613 Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1720847376.968419 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.