On this page
Troubleshoot MiniUp Publishing and Apps
Start troubleshooting with the exact Site or resource, the action attempted, and the visible error. Check whether the failure is in a draft preview, a published app, or an account management screen.
Diagnose common symptoms
| Symptom | Next step |
|---|---|
| Site upload fails | Check file format, name availability, file count, and current upload size limits |
| Blank published Site | Confirm root index.html, referenced assets, and browser-ready JavaScript |
| Update not visible | Confirm the right Site/file was saved and the intended version was published |
| Member cannot enter | Check signed-in account, invitation acceptance, current role, and Site Access |
| Data returns 401 or 403 | Check Table key/access settings and cross-site dataset grants |
| Function returns 404 or 405 | Check slug, implemented route, and allowed HTTP method |
| Function call quota reached | Read current Function usage, remaining allowance, and reset date |
| Data Source refresh fails | Test URL, credentials, schema, source availability, and import limits |
| Map is empty or misplaced | Verify geometry, coordinates, query area, and data access |
| PDF Pack fails | Review the job error and source PDF before retrying |
| AI result is incomplete | Review staged files, preview errors, model availability, and credits |
| Domain does not verify | Compare exact hostname and DNS records with the current domain panel |
Debug a published app
- Copy the actual published URL and reproduce the problem in the intended account.
- Check Site Access, dataset access, Function access, and published status for the affected resources.
- Inspect the browser’s visible request status or the Function Test result without sharing private credentials.
- Repair the relevant setting or file and rerun the same action.
- Test on another browser or phone when the issue concerns layout or browser access.
Example: an empty table after deployment
Distinguish a successful API response containing no records from a failed request. A 403 should produce an access error, not a “No records” message. Check the dataset grant and Table permissions before changing UI code.
When to request help
If the visible controls and linked guides do not resolve the issue, provide the public Site URL, feature name, action, time, and sanitized error. Do not send keys, passwords, private records, or Function Secrets. MiniUp’s FAQ includes its support contact.