claude-code - 💡(How to fix) Fix [Bug] Usage limits not updating after upgrading from Max 5 to Max 20 [1 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/yuvalmelnik/.local/share/claude/versions/2.1.114 (expected in multi-process scenarios)\n at sd_ (/$bunfs/root/src/entrypoints/cli.js:2751:2177)\n at WH8 (/$bunfs/root/src/entrypoints/cli.js:2751:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T08:07:31.335Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:26:38.757Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:26:44.461Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:26:51.003Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:26:56.700Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:27:02.543Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:27:08.249Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:27:16.651Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:27:27.197Z"},{"error":"McpToolCallError: {"error":true,"message":"{\"errorMessages\":[],\"errors\":{\"customfield_10157\":\"Operation value must be an Atlassian Document (see the Atlassian Document Format)\"}}"}\n at CJ7 (/$bunfs/root/src/entrypoints/cli.js:4759:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T12:27:32.173Z"},{"error":"Error: Tool mcp__plugin_atlassian_atlassian__getTransitionsForJiraIssue not found\n at N_7 (/$bunfs/root/src/entrypoints/cli.js:3089:30626)\n at JD (/$bunfs/root/src/entrypoints/cli.js:477:21015)\n at m$ (/$bunfs/root/src/entrypoints/cli.js:477:39569)\n at sHH (/$bunfs/root/src/entrypoints/cli.js:477:50282)\n at vO (/…

TL;DR

The issue might be related to incorrect configuration or compatibility problems after upgrading from Max 5 to Max 20, and verifying the account settings and tool configurations could help resolve the issue.

Guidance

1. Verify Account Configuration: Check if the account settings have been correctly updated to reflect the upgrade from Max 5 to Max 20, ensuring that all limits and features are properly configured.
2. Tool Compatibility: Investigate if there are any tool compatibility issues, especially considering the errors related to McpToolCallError and the missing mcp__plugin_atlassian_atlassian__getTransitionsForJiraIssue tool.
3. Atlassian Document Format: Review the operation values to ensure they comply with the Atlassian Document Format, as indicated by the error messages.

Example

No specific code example can be provided due to the lack of direct code references in the issue description.

Notes

The provided information is incomplete, and the content was truncated, which limits the ability to provide a comprehensive solution. Further investigation into the account configuration, tool compatibility, and adherence to the Atlassian Document Format is necessary.

Recommendation

Apply a workaround by verifying and adjusting the account configuration and tool settings to ensure compatibility with Max 20, as the issue seems to stem from potential misconfigurations or compatibility problems rather than a direct version upgrade issue.