CupixWorks 5.0 — this article is still being finished. Screenshots marked to be replaced show the right screens and will be retaken before launch. Taken from a pre-release build, so a supplier's trial watermark is visible over the table.
What a slow connection looks like
Network speed rarely produces a clear error. It produces repeated partial failure, which reads like a bug in the app.
Two patterns point at the connection rather than at CupixConnect:
| Symptom | What is happening |
|---|---|
| Uploading several files and only some arrive, needing retry after retry | Individual transfers are timing out before they finish. |
| Downloading a large SiteView repeatedly fails or never completes | The same, in the other direction, over a much larger payload. |
The speeds to aim for
| Direction | Minimum |
|---|---|
| Download | 100 Mbps |
| Upload | 10 Mbps |
Faster is better and the difference is not marginal — these are minimums for the work to complete, not targets for it to be comfortable.
Run a speed test from the machine running CupixConnect, on the network it will actually use. A site office on shared site wifi is not the same connection as the laptop was on yesterday.
What to do about it
Use a wired connection where one exists. For large uploads this is usually the whole fix.
Upload overnight if the connection is shared during the day. History resumes what did not finish, so an interrupted overnight run is not wasted work.
Clear the cache folder before retrying — see FAQ: Cache management — because a failed transfer can leave a part-written temporary file behind.