Configuration Export and Import

Where to find it

Open Configuration (the Team link in the top navigation goes there), then Workspace in its side menu; the page address ends in /configuration/workspace. The Configuration Export and Import card is near the bottom of that page. It holds the Export configuration button, the file picker, the Preview import and Import buttons, the import report, and the Import from another tool section. Export and import act on the organization you have selected. A member who is not an admin or owner of that organization gets the message “Only organization admins and owners can export or import configuration.”

What the file contains

Section	Included	Left out
Alert rules	Every alert rule of the organization: name, description, severity, evaluation interval, conditions, tags, and the name and type of each linked notification channel.	Notification channel settings, because they can hold credentials.
Automations	Every automation rule of the organization: name, description, trigger, actions and their settings, target scope and tag, schedule, minimum severity, trigger conditions and retry settings.	Webhook URLs, webhook headers and webhook body templates, because they can hold credentials. The file lists, for each rule, which of them were left out.
Reports	Your own saved Data Explorer views and the views shared with the organization: name, description, chart type and query.	Other members' private views.

The file starts with "format": "etducky.config" and "version": 1. An import refuses a file without that format, or with a newer version than the server reads.

Smart Reports questions are not saved as definitions, so they are not part of the file. Saved Data Explorer views are.

Importing a file

1. Choose the file with the file picker.
2. Click Preview import. The server checks every item against the organization and shows what the import would add and a report of anything that would be skipped or changed. Nothing is written.
3. Click Import to add the items.
4. Review each imported rule, fill in what the report names, and enable it.

An import never turns anything on. Imported alert rules and automations are disabled. Imported saved views are private to the member who imported them, and can be shared from Data Explorer.

A disabled automation does not run. Schedules and event triggers skip it, and Run Now answers “This automation is disabled. Run Now runs only enabled automations. Enable it in the rule editor, then run it again.”

What the import changes

Situation	Result
An alert rule names a notification channel	The rule is linked to the channel of the same name and type in this organization. When none exists, the rule is imported without that link and the report says so.
An alert rule fails the rule editor's checks (severity, an evaluation interval outside 10 to 3600 seconds, missing or invalid conditions)	The rule is not imported. The report gives the reason.
An alert rule's severity is not one the rule editor offers (critical, warning, info), such as error, High or Moderate	The rule is imported with the editor's level for it: Critical, High, Emergency, Major, Failed and error become critical; Moderate, Medium, Minor, Low and Warning become warning; Information, Informational and Notice become info. The report says “Imported with a change” and names both. A word none of these covers is refused as an invalid severity.
A name already exists in this organization	The item is imported anyway, and both are kept. The report says so for alert rules and automations.
An automation step runs a script that is not in this organization and is not a built-in script	The script is cleared from the step. Choose a script before enabling the rule.
An automation step sends to an alert channel that is not in this organization	The channel is cleared from the step.
An automation targets a tag that does not exist in this organization	The tag name is kept, and the report says the tag does not exist yet.
An automation assigns tickets to a member	The assignee is kept. A rule whose assignee is not a member of the organization fails when it runs.
An automation step in the file sets a webhook URL (an ET Ducky export never does, but a converted or edited file can)	The URL is kept, and the report names the host it points at. Check it before enabling the rule.
An automation's webhook URL, headers or body template were left out of the export	The report reminds you to enter them before enabling the rule.
An automation has no name, trigger or action, or a target scope other than triggering agent, all agents or tagged	The automation is not imported.
A saved view has no query or its query names no data source	The view is not imported.
Saved views on an organization without a paid subscription	Saved views are not imported. Data Explorer saved views need a paid subscription.
The organization already has 50 saved views	The remaining views are not imported.

Copying a configuration to another organization, step by step

Use these steps to back up an organization's alert rules, automations and saved views, or to copy them into another organization. You need to be an admin or owner of both organizations.

1. Export from the organization you copy from

1. Select the organization you copy from in the dashboard's organization picker.
2. Open Configuration, then Workspace, and find the Configuration Export and Import card.
3. Click Export configuration. The browser saves a file named etducky-configuration- followed by the date, for example etducky-configuration-2026-10-27.json, and the card says how many alert rules, automations and saved views it exported.

2. Prepare the organization you copy to

• Create the notification channels the alert rules use, with the same name and type as in the first organization, so the import can link them.
• Create the agent tags the automations target, and add them to the right devices.
• Add the scripts the automations run, unless they are built-in scripts.

Anything you skip here is reported by the import and can be filled in afterwards.

3. Preview and import

1. Select the organization you copy to in the organization picker. Switching organizations clears any file or preview the card was holding, so choose the file after you switch.
2. Open Configuration, then Workspace, and choose the exported file with the file picker in the Configuration Export and Import card. The card says “File loaded. Preview it to see what the import will do.”
3. Click Preview import. The card says how many alert rules, automations and saved views the import would add and how many it would skip, and ends with “Nothing has been imported yet.” Below it, a table lists each item the import would not import or would change, with its type, name, result (“Not imported” or “Imported with a change”) and the reason. When nothing needs attention it says “Every item imports as it is.” The table's reasons are described in What the import changes.
4. Click Import. The button appears only after a preview of the same file succeeds. The card says how many items were imported and that imported rules are disabled until you enable them. The report table stays on the card; keep it open while you review the items.
5. Review and enable each item as described in Reviewing and enabling imported items.

Importing the same file twice adds every item twice. Names may repeat, so delete the copies you don't need.

Reviewing and enabling imported items

Imported alert rules and automations are disabled, and imported saved views are private to you. Nothing runs and no one else sees a view until you change that.

Item	Where to find it	How to enable it
Alert rules	Alerts, then the Alert Rules tab. Disabled rules show with their switch off.	Click Edit, check the conditions, severity and evaluation interval, select at least one notification channel (the editor does not save a rule without one), tick Enable this rule and click Update Rule. The switch on the rule card also turns a rule on or off.
Automations	Automations, then the Rules tab.	Click Edit, check the trigger, schedule, actions and target scope, choose the scripts, channels and assignees the report names, enter any webhook values that were left out, tick Enabled and click Save Rule.
Saved views	Data Explorer, in your saved views.	Open the view to check its results, then share it with the organization from Data Explorer when it is ready.

A disabled automation does not run on its schedule or on events, and Run Now refuses it. To try an automation on a few devices first, set its target scope to a tag that only test devices carry before you enable it, then widen it (see Automations).

Importing from another tool

The Import from another tool section of the card drafts a configuration file from another RMM tool's alert rules, monitors, automations and reports. The draft is not imported until you preview it and click Import, and it imports the same way as any other file: rules disabled, views private. Drafting is for organization admins and owners, and it is part of every paid plan, including plans with agent seats only.

1. Optionally choose the other tool in the list: NinjaOne, Datto RMM, ConnectWise Automate, N-able N-central, Atera, Kaseya VSA, Tactical RMM, Level or Another tool. Leave it on Not named if you prefer. The choice names the tool to the AI. Choosing Datto RMM also gives the AI Datto's monitor types, alert priorities and policy terms, so monitors map more reliably.
2. Add up to 5 files, paste text, or both. Files can be screenshots (PNG, JPEG or WebP), PDFs, or export files (XML, JSON, CSV or plain text, in UTF-8, in UTF-16 with a byte order mark, or in Latin-1, also called ISO-8859-1). ZIP archives are refused: extract the files inside and upload those.
3. Click Draft with AI. The draft is made on the server while the card shows its progress: waiting for a drafting slot, drafting, or waiting to ask the AI provider again. Keep the page open. When the draft is done, the card shows what the AI could not map, the fields it left blank and its notes, then previews the draft as described in Importing a file. When something was not mapped, Request review asks ET Ducky to add it (see Requesting a review).
4. Click Import, or Download draft to keep the draft file and edit it first.

In the files	In the draft
Webhook URLs, webhook headers and webhook body templates	Always blank. Each one is listed under “Left blank: fill in after import”.
Any other value that looks like a key, token or password, a URL that carries a password or key, or an incoming-webhook URL	Blank, and listed under “Left blank: fill in after import”.
A script or component the other tool runs	A Run Script step. When exactly one approved script of this organization, or one built-in script, has the same name (ignoring case), the step uses it and a note says so. Otherwise the script is left to choose, and a note names the step and the other tool's script name. The draft never carries script code.
An email the other tool sends	A Notify step that sends to the organization's email alert channel (the first by name; a note asks you to choose another when the organization has several). When the organization has no email alert channel, the step emails the organization's admins and a note says so. The other tool's recipients are named in the notes: add an email alert channel for them.
A PSA or helpdesk ticket the other tool opens	A Create Ticket step. It opens an ET Ducky ticket; the other tool's ticket settings (priority, queue, issue type, work type) are written into the ticket title. A note says so, and says when no ticketing integration is connected. Ticket integrations and assignees are never set by a draft.
Notification channels of alert rules	Not linked. Link channels in the alert rule after import.
A condition on a metric ET Ducky does not read, an automation trigger that ET Ducky does not fire (Agent Went Offline, Agent Came Online), or an action ET Ducky does not have	The item is listed under “Not mapped” and left out of the draft.
A schedule	A standard 5-field cron expression that runs in UTC (see Automations), converted from the other tool's time zone when the files show it. A schedule cron can't express, such as seconds, the last day of the month or the second Tuesday, is listed under “Not mapped”.
A report	A saved Data Explorer view over the last 7 days, when its query passes Data Explorer's checks. Views on a data source that needs a privilege are listed under “Not mapped”.
Anything that fails the checks an import applies, or that the AI reports it could not map	Listed under “Not mapped” with the reason, and left out of the draft.
Things the AI could not see, such as collapsed panels, script bodies, or schedules on another tab	Listed under “Notes from the AI”.

The AI is told to treat everything in the files as data and to ignore instructions written in them. Its answer is then checked item by item, so only items that pass the checks reach the draft.

What imports from other tools

The draft keeps each item's own name from the other tool, for example a monitor named “Windows Defender Antivirus (Running And Up To Date)” stays that name. Alert priorities become the rule editor's severities as described in What the import changes. These kinds of items import as working ET Ducky items, still disabled until you enable them:

In the other tool	In ET Ducky
CPU, memory and disk monitors with a threshold and a duration	An alert rule on the matching metric, held for the same duration.
Device offline or online status for N minutes	An alert rule on Seconds since last contact greater than N times 60.
Antivirus status: not running, disabled or real-time protection off	An alert rule on Antivirus enabled equal to 0.
Antivirus status: definitions not up to date, or older than N days	An alert rule on Antivirus definitions up to date equal to 0, or Antivirus definition age greater than N.
Antivirus “running and up to date” not detected (for example a Datto RMM Antivirus Status monitor)	One alert rule with both conditions, the second joined with OR.
Patch monitors: updates pending or missing	An alert rule on Pending updates (last patch scan). The count comes from ET Ducky's patch scan, so the device needs patch scanning turned on.
Patch monitors: no update installed for N days, or Windows Update turned off	An alert rule on Days since an update was installed, or on Windows Update enabled equal to 0.
Patch monitors: a patch failed to install	An alert rule on Failed patch jobs, last 24 hours greater than 0. It counts ET Ducky patch jobs that failed, regressed or were rolled back, so it applies to devices whose patches ET Ducky installs.
Patch monitors: security or critical patches missing	An alert rule on Pending security and critical updates greater than N (greater than 0 when any missing one alerts). The count comes from ET Ducky's patch scan, so the device needs patch scanning turned on.
Service monitors: one named service stopped or not running	An alert rule on Service running equal to 0, with the service as the condition's target. See Conditions with a target for which services the agent reports.
Service monitors: any automatic service stopped	An alert rule on Automatic services stopped greater than 0.
Event log monitors: an event id, optionally from one source, seen in a log	An alert rule on Event log entries (count) greater than 0 (or greater than N), with log|event ids|source as the target and the other tool's lookback as the window. Windows agents 2.8.5.1 or later; a note says so.
File and folder size monitors	An alert rule on File size or Folder size greater than N MB, with the path as the target. Agents 2.8.5.1 or later.
Ping monitors	An alert rule on Ping loss (equal to 100 when the host does not answer, greater than N for packet loss) or Ping round trip greater than N ms, with the host as the target. Agents 2.8.5.1 or later.
Events that fire once: software installed, software removed, a device enrolled, a security detection	An automation on the matching trigger (Software Installed, App Removed from Inventory, Agent Enrolled, Security Detection) with a Notify step whose message names the event and the other tool's severity. App Removed from Inventory fires once the application has been absent from every device for 7 days.
What a monitor does when it alerts: run a script or component, send an email, open a ticket	An automation on the Alert Fired trigger that answers only that rule (its first condition is Alert Rule Name equals the rule's name), with one step for each response, linked as the table above describes.
Auto-resolve when the issue stops	Nothing to set: ET Ducky resolves an alert at the first check where its condition no longer holds. A fixed wait before resolving has no setting and is noted.

Still listed under “Not mapped”, because ET Ducky has no data for them yet: SNMP, performance counters, process monitors, custom script or component monitors, file and folder size on a network path, the state of one antivirus product's own agent, and rules for one named update. Use Request review to ask ET Ducky to add one.

Requesting a review

When a draft lists anything under “Not mapped”, or drafts nothing, the card shows Request review below the AI's report. It sends ET Ducky a request to add what the draft could not carry over.

1. Optionally type a one-line comment, for example why the item matters to you.
2. Leave Attach the files I uploaded unticked to send only the draft's report, or tick it to include the files and pasted text you used for the draft.
3. Click Request review. The card says “Review requested. ET Ducky will reply by email” followed by the address the reply goes to.

Sent to ET Ducky	When
The organization's name and id, your name, email and user id, the tool chosen for the draft, the AI's description of each item it saw, each item not mapped with its reason, the AI's notes, the fields left blank, the draft itself (its secret fields are already blank), the names, types and sizes of your files, and your comment	Always.
The text of your text files and PDFs, and your pasted text	Only when you tick Attach the files I uploaded. The browser sends them again; anything that looks like a key, token or password is removed before they are stored in the review ticket at ET Ducky.
Screenshots	Never stored: review tickets have no attachment storage. Their names, types and sizes are listed, and ET Ducky may ask you for them by email.

Without the box ticked, your files stay as the card describes them: read for the draft only and not stored. Only organization admins and owners can request a review, only for a draft they made, and once per draft. A draft is kept for one hour after it finishes, so request the review within that hour.

What to upload from each tool

The draft reads what it is given: screenshots (PNG, JPEG or WebP), PDFs, and text files such as XML, JSON, CSV or plain text, plus text pasted into the box. It does not connect to the other tool. Which of these you can get depends on the tool. The table below says what is known about each tool in the list; where a tool's own export is not described here, export or screenshot the rule list from the other tool.

Tool in the list	What to upload
Datto RMM	Screenshots of each monitoring policy and each monitor in it, with the monitor type, threshold, duration and alert priority visible, or a PDF of those pages. Datto RMM's published API documents no export of monitors or monitoring policies, so screenshots are the usual source. Choosing Datto RMM gives the AI guidance for Datto's monitor types: CPU, Memory, Disk Usage, Online Status, Antivirus Status and Patch monitors, and Service monitors (one named service, or stopped automatic services), are mapped to ET Ducky metrics, and a monitor's response components, emails and PSA tickets become an Alert Fired automation (see What imports from other tools). Event Log, Ping and File/Folder size monitors are mapped to the agent watch list metrics. Process, Component, SNMP and performance-counter monitors are listed under “Not mapped”, because ET Ducky has no metric for them. A policy's site or filter target does not carry over; ET Ducky alert rules cover every device in the organization.
N-able N-central	N-able's documentation describes exporting a service template from Configuration > Monitoring > Service Templates with Export in the template's row, which saves ServiceTemplateExport.zip holding XML. The draft does not read ZIP files: extract the archive and upload the XML inside (at most 5 files per draft). Screenshots of the template's services and thresholds also work.
Kaseya VSA	Kaseya's VSA 9 documentation describes the Import Center (System > Server Management > Import Center) exporting monitor sets, SNMP sets, event sets, agent procedures, patch policies, policies, reports and views into one XML file. Upload that XML. All text in one draft, files and pasted text together, can be at most 120,000 characters, so export a few items at a time. Files saved in ISO-8859-1 (Latin-1) are read as such.
NinjaOne, Atera, Level, ConnectWise Automate	No export of monitors, policies or automations is described here for these tools. Upload screenshots of each policy, monitor, condition and scheduled task with its settings expanded, a PDF printed from those pages, or text copied from them.
Tactical RMM	Screenshots of the checks, automation policies and tasks with their settings visible, or text copied from them. JSON you already saved from Tactical RMM's API is a text file the draft can read.
Another tool, or not named	An export file when the tool offers one in XML, JSON, CSV or plain text; otherwise screenshots, a PDF or pasted text. The AI is told only that the material comes from another RMM tool.

For any tool, the draft maps what the files show onto ET Ducky's alert metrics (see Alerts), automation triggers and actions (see Automations) and Data Explorer data sources (see Data Explorer). A monitor on something ET Ducky does not measure, such as an SNMP value, is listed under “Not mapped”. A script the other tool runs becomes a Run Script step whose script you choose after import; the draft does not carry script code.

Moving a setup from another tool, step by step

Use these steps the first time you move alert rules, monitors, automations or reports into ET Ducky.

1. Prepare ET Ducky

• Install agents on at least a few of the devices the rules are for, so you can test them after import (see Agents).
• Create the notification channels, tags and scripts the rules will need. An import links an alert rule to a channel of the same name and type, keeps tag names, and keeps scripts only when they already exist in the organization or are built in.

2. Collect material from the other tool

• An export file is the most complete source when the other tool offers one. Use XML, JSON, CSV or plain text. See What to upload from each tool.
• Otherwise take screenshots of each rule, monitor, automation or report with its settings expanded, so the conditions, thresholds, schedule and actions are visible. Settings in collapsed panels, on other tabs or inside script bodies are not seen.
• Include the time zone a schedule runs in when the other tool shows it. Without it, check each converted schedule after import.
• Remove passwords, API keys and tokens from export files before you upload them where you can. The draft leaves values that look like secrets blank in any case.
• Group the material by kind or by policy. A draft takes at most 5 files and holds at most 100 items of each kind, and an organization can make as many drafts as it needs.

3. Draft, preview and import

1. Open Configuration, then Workspace, and find Import from another tool in the Configuration Export and Import card.
2. Choose the other tool if it is listed, add the files or text, and click Draft with AI.
3. Read the “Not mapped”, “Left blank: fill in after import” and “Notes from the AI” lists. Keep a copy: click Download draft if you want the file.
4. Check the preview, then click Import. Repeat for the next group of material.

4. After the import

Everything imported is off until you turn it on (see Reviewing and enabling imported items for where each item is). For each imported alert rule and automation:

• Open it in the rule editor and compare it with the original: conditions, thresholds, severity, evaluation interval and target scope.
• Link the notification channels of alert rules.
• Choose the script for each run_script step, and the alert channel, ticket integration or assignee for steps that need one.
• Enter webhook URLs, headers and body templates listed as left blank.
• Check each schedule. Schedules run in UTC.
• Create any tag the import report says does not exist yet, and add it to the devices the rule is for.
• Enable the rule. To try an automation on a few devices first, set its target scope to a tag that only test devices carry, then widen it (see Automations).

Rebuild by hand the items listed under “Not mapped”, or leave them out where ET Ducky covers the need another way. Imported saved views are private to you; share them from Data Explorer when they are ready.

Limits and records

• A file may carry at most 500 alert rules, 500 automations and 500 saved views, and may be at most 4 MB.
• Every export and every import (not a preview) is recorded in the organization's audit log with the number of items.
• An AI draft takes at most 5 files of up to 4 MB each, 10 MB in all, and 120,000 characters of text. The file type is read from the file's content, not its name, and other types are refused.
• Files and text for a draft are sent to the organization's AI provider for that one draft: the organization's own key when BYOK is set, otherwise ET Ducky's provider. ET Ducky does not store them. The ET Ducky server that receives them keeps them in its memory only until the draft is finished. The finished draft is kept for an hour so the card can show it, then deleted.
• An organization without a paid plan gets the answer “AI drafts are part of every paid ET Ducky plan, including plans with agent seats only.” There is no limit on how many drafts an organization makes.
• Each draft uses queries from the organization's AI query pool, metered by tokens, unless the organization's own BYOK key makes it (see AI Usage). When the pool is used up and the organization has no key of its own that works, the draft fails with a sentence that says how to get more queries or add a key.
• When the organization's own key refuses or fails a draft, ET Ducky's provider makes the draft instead. The card then says that the draft was charged to the organization's AI queries.
• When the organization's own key does not accept PDF files (for example an Azure OpenAI deployment without PDF input), ET Ducky reads the text of each PDF on its own server and sends that text with the same key instead. The key is not marked as failing, nothing is charged to the AI queries, and the card says the PDF's text was sent; images, tables and layout in the PDF are not sent. A PDF with no text ET Ducky can read, such as a scanned page, ends the draft with a sentence asking for screenshots or pasted text.
• When the AI provider does not answer in time, limits requests or returns a server error, the draft is tried again up to three more times, after 20, 60 and 120 seconds, and the card shows the wait. When the organization's own key does not answer in time and the organization has no AI queries left for ET Ducky's provider to take over, the draft fails at once instead of waiting. When the card gets no answer from ET Ducky while it checks on a draft, for example during a network interruption, it says it is waiting and checks again; the draft keeps running on the server.
• Each ET Ducky server makes a few drafts at a time, at most two of one organization's at once, and other drafts wait their turn; there is no limit on how many wait. When a server is holding as many waiting uploads as it can, the card sends the draft again after a short wait. If the server holding a draft's files stops before the draft is done, the draft fails, because the files were never stored.
• When a draft fails, the card shows a Retry button. A request the server refuses before drafting starts, such as a file over the limits or an organization with no paid plan, is not a failed draft and shows no Retry. It starts a new draft from the same files, vendor and text, which the browser still holds; ET Ducky's servers never stored them. If you changed the chosen files or the text since, or left the page, the card asks you to choose the files again and click Draft with AI.
• A draft holds at most 100 items of each kind. Upload fewer items at a time for more.
• Every AI draft is recorded in the audit log with the number of files and items, never file names or contents.
• A review request is recorded in the audit log with the number of items not mapped, the number of files and whether they were attached, never the draft, the comment or file contents. Review requests share the Contact form's limit of 5 a minute from one address.

Troubleshooting

The card says	What to do
“Only organization admins and owners can export or import configuration.”	Ask an admin or owner of the selected organization, or check that the organization picker shows the organization you meant.
“This is not an ET Ducky configuration file.”, “This configuration file has no format version.” or “This configuration file was written by a newer version of ET Ducky and can't be imported here.”	Choose a file made by Export configuration or Download draft. A file exported from another RMM tool goes in Import from another tool, not in the file picker above it.
“Preview the file before importing it.”	Click Preview import first. Choosing another file or switching organizations clears the preview.
“Add a file or paste text from the other tool.”, “Upload at most 5 files at a time.”, a file “is larger than 4 MB”, or “The files are larger than 10 MB together.”	Split the material into several drafts.
A file “is not a PNG, JPEG, WebP or PDF file, or a text file (XML, JSON, CSV or plain text).”	The type is read from the file's content. Extract ZIP archives and upload the files inside; save other formats as a screenshot, a PDF or text.
“The text is longer than 120,000 characters. Upload fewer items at a time.”	Export or paste fewer items per draft.
“AI drafts are part of every paid ET Ducky plan, including plans with agent seats only.”	The organization has no paid plan. Subscribe or buy agent seats, then draft again.
“This organization has used all of its AI queries for this month, and it has no AI key of its own.”	Add the organization's own key on the AI API Key (Bring Your Own) card under Configuration (see BYOK), add a query subscription or agent seats, or wait for the monthly quota to reset.
“Your organization's own AI key could not make this draft, and ET Ducky's AI provider could not take over ...”	Check the key's status on the AI API Key (Bring Your Own) card. The draft could not fall back to ET Ducky's provider because no AI queries were left.
A wait such as “The AI provider did not answer in time. Trying again in 20 seconds (attempt 2 of 4).”	Keep the page open. The draft is tried again on its own.
“The AI provider did not answer after 4 tries. Try again in a few minutes.” or “The AI could not make this draft right now. Try again later.”	Click Retry later. It sends the same files again as a new draft.
“The AI's answer could not be read as a configuration draft. Try again, or with fewer files.” or “The files describe more than one draft can hold. Upload fewer items at a time.”	Split the material into smaller groups and draft each one.
“The ET Ducky server that was making this draft stopped before it finished.”	The uploaded files were held only in that server's memory. Click Retry, or choose the files again and click Draft with AI.
“Your organization's own AI key does not accept PDF files, and ET Ducky could not read any text in ...”	Upload screenshots of the PDF's pages, or paste its text.
“Waiting for ET Ducky to answer. The draft keeps running on the server ...” or “Waiting for the network to come back.”	Keep the page open. The card checks again on its own.
“A review of this draft was already requested.”	ET Ducky has the request. Each draft can be sent for review once.
“This draft is no longer available. ...”	A draft is kept for one hour. Draft it again, then click Request review.
“The files of this draft are no longer held in this page. ...”	The browser no longer holds the files, for example after a page reload or another draft. Untick Attach the files I uploaded, or draft again.
“Review requests are not available right now. ...”	Try again later, or email support@etducky.com.
“ET Ducky did not answer the request to start the draft. Try again.” or “The upload is larger than the server accepts.”	Click Draft with AI again, with at most 10 MB of files.
“The draft is taking too long to report back. Try again later.”	The card stops checking after 45 minutes. Draft again later.
“This draft is no longer available.”	Finished drafts are kept for an hour. Draft again.
“The organization changed while the draft was made. Draft again.”	The organization picker changed during the draft. Select the organization again and draft again.
“The files and text of that draft are no longer chosen here.”	Retry works only while the same files and text are chosen. Choose them again and click Draft with AI.
“The AI drafted nothing that ET Ducky can import.”	Read the “Not mapped” list. Upload clearer screenshots with the settings expanded, or rebuild those items by hand.