{"ops":[{"insert":"Unfortunately, there seems to be a bug with Archidekt's keyboard shortcuts (such as \"m\" to move to maybeboard, \"-\" to remove cards, etc.) causing it to crash the user's UI temporarily. If a user uses a shortcut key many times in a row, it can cause an error. For me, it usually happens after using it around 30-40 times in a row. The error is listed as \"Failed to save changes\". Clicking to view details shows the following:\nError saving deck changes"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"There was an issue saving your deck. All changes have been undone. Editing will attempt to save again. If you continue to have issues, please contact support via email, discord, or our forums."},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"\nRefreshing the page afterward shows another error, as does trying to go to the \"My Decks\" page: \"Data fetching error: "},{"attributes":{"background":"#f9fafb"},"insert":"An error happened while fetching data from our API\""},{"insert":"\n\nAfter about a minute, the error seems to resolve itself, and the user can access the deck again. This is really annoying when trying to make large scale edits to a deck. For me, I keep running into the error when crafting my decks. Usually when I'm trying to add all cards of a specific type to the maybeboard, or I'm trying to move many cards from the maybeboard into the main deck. I also have the issue if i'm trying to remove a lot of cards (such as when removing all cards of a specific color to change commanders). Please fix this error.\n\nSimple example to repeat the error:\nStart with a deck with 50 or more unique cards in the main deck"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"Ensure you're in the \"Text\" layout (it may work in other layouts too, but this seems easiest)"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"Using the \"m\" key as a shortcut, move each card to the maybeboard one after another"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"After 30-40 cards, the error should occur"},{"attributes":{"list":"bullet"},"insert":"\n"},{"insert":"\nIt may be worth noting that I'm using Google Chrome, but I'm guessing that won't make a difference, as the issue seems to be occurring when syncing with a database.\n\n\nThe request and error details are shown below:\n\n"},{"attributes":{"bold":true},"insert":"Request:"},{"insert":"\n{\n \"updatedCards\": [\n {\n \"action\": \"modify\",\n \"cardid\": \"122004\",\n \"categories\": [\n \"Theft\"\n ],\n \"patchId\": \"LHALoZIyP6DB\",\n \"modifications\": {\n \"quantity\": 1,\n \"modifier\": \"Normal\",\n \"customCmc\": null,\n \"companion\": false,\n \"flippedDefault\": false,\n \"label\": \",#656565\"\n },\n \"deckRelationId\": \"2268197695\"\n }\n ]\n}\n\n"},{"attributes":{"bold":true},"insert":"Error:"},{"insert":"\n{\n \"detail\": \"Request was throttled. Expected available in 29 seconds.\",\n \"statusCode\": 429\n}\n\n\n"}]}
0
{"ops":[{"insert":"The error you posted has your answer. \n\nRequest was throttled. Expected available in 29 seconds"},{"attributes":{"blockquote":true},"insert":"\n"},{"insert":"\nYou're getting throttled for having too high actions per minute, the site thinks you're spamming. I'd suggest using multi select and move a bunch of cards at once if this problem is happening regularly. Using multi select will do a single action, rather than 40+ very quickly. \n"}]}
1