Have you ever seen an "Alert detected during processing" message when trying to publish a dataset? Or maybe a colleague reported missing rows in a dataset that published without throwing a hard error?
When a dataset hits a limit during processing, publication can either fail completely or stop partway, leaving some of your data or sources out. Here is a quick breakdown to help you identify the cause and get your dataset published.
🔍 1. First, check the message type
Before diving into troubleshooting, check how the error begins in your back office (Asset Settings or Content page):
-
Alert detected during processing:follow the steps below! This means a quota, workspace setting, or platform threshold was reached. -
Error during processing:this is not a quota issue. Check if your source URL/file is reachable or if the schema/structure changed.
💡 Email vs. Back Office: email alerts tell you a limit was reached, but not which one. Always check the message inside the dataset’s back-office page for the exact details (and click the More details panel if available).
🛠️ 2. Common limits & what to do
| Alert / Message | What it Means | What to Do |
max. Dataset Size reached | You hit the maximum number of records allowed for a single dataset. | Check your plan limits or workspace limits (Access > Security). Note: this counts row/record count, not file size in MB/GB! |
max. Published Data (GB) reached | Total size limit for published local datasets in your workspace. | Review your workspace storage usage under Settings > Plan. |
max. columns of the same type reached | Platform limit for how many columns of a single data type one dataset can hold. | Remove excess columns of that specific type and republish. |
| Other custom limits | Specific account/plan threshold reached. | Contact Support with the full error text. |
⚙️ 3. Check workspace vs. plan limits
If you reached a record limit, it might not be your main account plan stopping you! Domain administrators can set lower record caps per workspace:
-
Go to Access > Security > Data volume.
-
Check "Max number of records by dataset."
-
If this limit is lower than your plan's maximum, ask your domain admin to raise it, then unpublish and republish your dataset.
💡 Pro-tips & edge cases
-
Partial data loading: if a dataset crosses a record limit midway, it won't necessarily fail entirely. It loads records in batches until the limit is crossed and drops the rest. If you're missing rows or entire secondary sources, check for limit alerts!
-
"It fixed itself!" Did a failed dataset publish on its own later? Refused attempts aren't automatically re-tried, but scheduled republications will try fresh. If workspace space was freed up in the meantime, the next scheduled run will succeed.
-
Can't see the plan page? You need the "edit workspace properties" permission. If you don't see it, reach out to your domain administrator for assistance.
💬 Need more help?
- Check the documentation made with love by
@yier.wu and @patrick.smith in the User Guide.
-
Contact Support if your quota looks low but publication is still blocked.
-
Contact your domain admin to adjust workspace caps or review permissions.
-
Contact your CSM / Account manager if you need to upgrade your overall plan quotas.