Save and manage submission drafts
Save an unfinished new custom or Quick submission without starting a run.
Submission drafts are private snapshots of new-submission forms, including custom and Quick submissions. They are not drafts of existing results, running jobs, or continuation dialogs. Blog drafts and Problem Builder workflows are separate features. An existing custom submission opened for editing is a starting point for a new child submission; saving that new form does not alter its parent.
Save without submitting¶
Choose Save draft in the floating form controls beside Submit and Reset. Quick forms offer it on their problem and GA-parameter steps. Incomplete or invalid fields can be saved; you do not need a runnable fitness function yet. Saving does not enqueue optimization or charge for a genetic run.
A notification confirms Saved as draft. This submission has not been submitted. Further saves on that page update the same draft. If you edit while a save is in flight, those newer changes remain unsaved. A failed save keeps your form intact and shows an error. Save is manual, not automatic.
Resume or delete¶
Open Drafts from the left sidebar. In collapsed navigation it remains available as a labeled save icon. Choose Continue editing to reopen a draft; Quick drafts return to their original problem form. Continue editing, save again, or submit when ready.
Submitting does not automatically delete a saved draft. Delete unneeded drafts from the Drafts page. Deletion is permanent and does not use the submission Trash. Deleting a draft does not delete a run you already submitted from it. Only the owner can list, reopen, update, or delete their drafts.
What is and is not saved¶
Drafts preserve form inputs such as parameters, code text, checkboxes, supported dynamic rows, and sliders. They do not save file contents or the separate LEGA chat. Reselect custom data attachments and any Quick-form dataset/code uploads after reopening. Closing an attachment modal on the same page keeps the current file selection, but that is different from saving those files in a draft.
A draft request must fit within the 1 MiB request limit. Very large pasted code or form content can exceed it; the save error leaves your form available for correction. Browser refresh and navigation warnings help protect unsaved work, but do not replace saving a draft. Separate tabs are not a collaborative editor; avoid editing the same draft in multiple tabs at once.