We have extensive experience using Logic in courses built in Evolve and exceeding the same 64 KB Suspend Data limit within our own LMS, and client LMSs.
Evolve has a guide to Logic, and I think the following page from it is pertinent to your question:
On this page, it states in bold, “We recommend that the suspend data limit should be at least 64kb for the average sized course (3 pages with around 5-10 components per page).”
I think our smallest course has ten pages, maybe, and our older ones definitely have more than five to ten components each per page
The only proper solution to this is to have the option in your LMS to extend or remove the Suspend Data limit. The page linked above shows how to do this if you have access to the admin settings within SCORM Cloud or Moodle.
We use TalentLMS currently, and have asked them if they are able to extend or remove the Suspend Data limit. Unfortunately, they are not currently looking to do that and have no plans on their roadmap to do so in the near future
It is also not that common for clients to be able to do this in the LMS they use as they might be a client themselves of another company that sets up and controls the LMS they use, or their LMS might simply not have that option.
Suspend Data issues have been known about for a long time yet, it seems, that many LMSs have this limitation included in them, with zero or limited options to change.
After a lot of testing, the unfortunate outcome is if you HAVE to include certain features such as Bookmarking in longer courses containing long Pages full of Components, and/or a lot of Variables and Triggers (our courses range between 0 and 461 Triggers and 0 to 194 Variables used), the only “solution” is to enable the Local Storage Extension if you keep running into issues.
I say “solution” in double quotes because it can actually cause further issues itself. The TL;DR of Local Storage is that it utilises the user’s browser to store interaction information, such as what they have completed in the case of SCORM + Bookmarking, and works in conjunction with the information saved by the LMS itself.
However, this completely removes device agnosticism and even browser agnosticism on the same device for a user i.e. if they get partway through the course on their Laptop, and then later on decide to log back into the course on another device, like a Phone or Tablet, then their progress won’t be saved and they will have to start that same course from the beginning (or they will see some wacky stuff depending on the Logic included in the course).
Similarly, if they start the course on their Laptop using Google Chrome, and then switch to Mozilla FireFox to pick the course back up, they will have to start the same course from the beginning.
Furthermore, this will affect you and your colleagues when testing courses because even if you Duplicate a course within Evolve, work on it, re-Publish, and upload to the same LMS, the course will still grab bits of information saved in the browser from the previous course incarnation, and the course features you were expecting to have been fixed, even after a reset of progress within the LMS, will not work correctly.
We even have unconfirmed reports of the above issue even when using a different LMS for testing the same course within the same browser.
The workaround for the testing issue is that you will have to reset your progress in that course within the LMS, log out of your LMS, and then delete your internet browser history, including cookies, to a point before you first opened that course’s first incarnation in your LMS. This can be a very bad thing if you don’t know all of your logins for the various platforms and apps you use, as that information will be deleted. It is also a terrible thing to tell clients, and for you or clients to tell users to do, because of the above downsides.
Although it looks like you’re not using it, xAPI files tend to exceed the Suspend Data limit of 64 KB more often than the SCORM + Advanced Tracking due to xAPI sending data for every interaction (viewing, clicking, interacting, etc) rather than the limited data sent by SCORM files.
A downside of SCORM files versus xAPI files is to do with re-interactable MCQs. For the xAPI files, if it is working correctly and not exceeding your LMS Suspend Data limit, the MCQs are re-interactable for the user, where they can freely be set to “Show Answer” if the user got the answer wrong when they answered it intially, and come back to it after logging out and logging back in again.
For the SCORM files, the MCQs are re-interactable to “Show Answer” while the course is open, but if a user logs out and logs back in again, the MCQs are no longer re-interactable and only show a Tick or Cross depending on whether they got it right or wrong when they first answered it.
Sorry for waffling on, but feel free to let me know if you have any follow-ups in a Reply.