[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-31 UTC."],[[["Error messages should clearly state the problem, including specific details like sizes, limits, or timeouts, instead of generic phrases."],["Include information about why the error occurred, such as user permissions or system constraints, to aid user understanding."],["Offer solutions or further guidance by linking to relevant resources or explaining how to resolve the issue, enhancing the user experience."]]],["Users need clear, specific details about system limitations. Instead of vague messages, provide concrete information, like the exact size of attachments exceeding the limit (e.g., \"14MB exceeds 10MB\") or the precise timeout period (e.g., \"30s\"). When indicating permissions issues, specify the group with access (e.g., \"\u003cgroup name\u003e\"). Provide context on what is exceeding the limitations, and then provide a way to solve the issues.\n"]]