Overview
Start with the symptom in Assignment Importer, then check the relevant file, connection or Import Row. Record the error before retrying, especially when an Import Run may already have created Assignments.
At a glance |
|
Who can do this | Active Mobaro Users; a write-enabled organization API key is needed to import. |
Where | Assignment Importer › Project Settings › Mobaro API Log |
Works on | Assignment Importer desktop app (Windows x64 / macOS Apple Silicon) |
Availability | Contact your CSM |
Check the symptom
Symptom | How to check | What to do |
Sign-in does not complete | Check whether the app is waiting on the browser or an in-app dialog. | Use Cancel Login, then Open in browser. Complete fresh verification with an active Mobaro account. |
Mobaro rejected the API key | Use Test connection in Project Settings. | Check the key and target organization with the administrator. Do not put the key in a support message. |
Could not reach Mobaro | Check network access and the error’s timing. | Restore connectivity and retry the read-only connection test before an import. |
Connection succeeds; import fails | Read the failed request in Mobaro API Log. | A read test does not confirm write access. Check key permissions and the response details. |
Reference choices are missing | Inspect Mobaro Reference Data and Reload progress. | Check the key, then Reload Mobaro Data. Confirm the required choices exist in the target organization. |
An Import Row stays ? | Hover the status to read missing fields. | Complete the required fields and ensure the title template resolves to nonblank text. |
Attachments are missing | Check the folder, reference column, mode and exact filenames. | Repair the source files; back up before re-scanning embedded attachments. |
Import only partly succeeds | Read failed-row numbers, first error and C rows. | Save successful IDs. Reconcile uncertain outcomes in Mobaro, then retry only work still needed. |
Failed to save project | Check the file’s folder, write access and availability. | Restore access and save again. Keep the app open if unsaved created IDs need preserving. |
Project is unavailable or will not open | Check file location and whether the app requests a newer version. | Make the file local, locate it using Open Existing Project, or update the app if required. |
Collect useful diagnostics
1. Open the API request log
Open Project Settings › Mobaro API Log and choose Open API Log. Requests are captured for the current session.
2. Inspect the failed request
Select a request, then read Headers, Payload and Response. Capture the request URL, method, status code, timing and relevant error text. The log masks API keys, but request/response content can still contain organization data.
3. Prepare the support details
Include app Version and Channel, operating system, the action you attempted, the time, the exact error and affected Import Row numbers. State whether any rows show C, whether Save Project succeeded, and whether the issue repeats with a small fictional example. Send only the necessary redacted details through your usual Mobaro Support channel.
🛑 Critical: After a timeout, interruption or failed save, do not rerun the whole workbook simply because rows look ready. Check for Assignments already created in Mobaro. Assignment Importer has no automatic rollback of successful work.
For startup or file errors that do not produce an API request, Mobaro Support may ask for the app’s local diagnostic logs. These are stored in the per-user app-data logs folder and retained for seven days. Record the problem promptly and review the requested files for sensitive information before sharing.
Best practices
Keep the original workbook and current Import Project intact while diagnosing.
Use a fictional reduced example when possible; never share an API key.
Capture the API log before ending the session.
Frequently asked questions
Why is the API log empty?
Mobaro API Log shows requests captured in the current session. Local workbook, sign-in or file-save failures may not issue a Mobaro API request.
Does a failed request mean nothing was created?
No. A lost response can leave the outcome uncertain. Check Mobaro for the affected work before retrying to avoid creating duplicates.
Can Support diagnose the issue from a screenshot alone?
A screenshot helps, but include the exact error, Version, Channel, action, affected rows and whether the Import Project saved. Share relevant redacted request details when the failure involves the API.