# loopio project export failed 500: how to fix it

A 500 on Loopio project export usually means the export job crashed on one oversized or malformed piece of content. Export in smaller chunks to find the section that breaks it, then fix that section and export whole. If every chunk fails, it is a platform issue and support needs the project ID.

```text
loopio project export failed 500
```

## When to use this skill
- Project export returns a 500 error
- The export spinner dies with a generic failure message

## When not to use this skill
- Export succeeds but formatting looks wrong (a template issue, not a crash)
- You get a 403 or login error (permissions, not export)

## Tool compatibility
Loopio cloud. DOCX and PDF project exports.
Related area: business SaaS platforms and vendor portals.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with project export returns a 500 error, start at step 1 below.
- If instead export succeeds but formatting looks wrong (a template issue, not a crash), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Retry once to rule out a blip

```
Wait two minutes and run the same export again.
```
Expected: success on retry means it was transient. A second 500 means a real content problem.

### 2. Export section by section

```
Duplicate the project, delete half the sections, and export. Keep halving until it succeeds.
```
Expected: one half exports cleanly, which isolates the broken section.

### 3. Fix the broken section

```
Look in the isolated section for giant pasted tables, embedded objects, or corrupt images, and replace them with clean content.
```
Expected: the section exports on its own.

### 4. Export the full project

```
Go back to the original project and run the full export.
```
Expected: export completes and the file downloads.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (retry once to rule out a blip): Expected: success on retry means it was transient. A second 500 means a real content problem.
- Step 2 (export section by section): Expected: one half exports cleanly, which isolates the broken section.
- Step 3 (fix the broken section): Expected: the section exports on its own.
- Step 4 (export the full project): Expected: export completes and the file downloads.

## Quick recap
1. Retry once to rule out a blip
2. Export section by section
3. Fix the broken section
4. Export the full project

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### loopio export 500 error
Same bisect approach, the crash is almost always one bad section. If this matches what you saw, the steps above apply as written.

### project export failed loopio
If every chunk fails, open a support ticket with the project ID. If this matches what you saw, the steps above apply as written.

## Why it happens
The export renderer builds the whole document in one pass, so a single piece of content it cant render (a corrupt image, a table with merged cells pasted from a web page) crashes the job with a generic 500.

## Edge cases
- Exports over roughly 150 pages time out more often, export in parts
- Embedded videos never survive export, link them instead
- A 500 on every project means a platform incident, check status first

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Yb_F1ncWdrVHVg1GUDblVw