Core Concepts
System Limits & Quotas
Understanding Markifact data limits, execution history, and workflow runtime constraints.
Markifact has some built-in limits to ensure smooth performance for everyone. Here’s what you need to know about data sizes, execution history, and workflow runtimes.
After this period, execution logs are automatically deleted to keep your workspace clean.
Data Size Limits
Workflow Data Limit
Maximum total data per workflow: 20 MB This is the total amount of data that can flow through all nodes in a single workflow run. If your workflow pulls large datasets from multiple sources, keep this limit in mind.Individual Node Limit
Maximum data per node: 15 MB Each node can handle up to 15 MB of data. This applies to nodes that pull reports, generate content, or process information. What happens if you hit these limits?- Your workflow will stop running and show an error message
- You’ll get a clear explanation of which node exceeded the limit
- No credits are charged for failed nodes
Execution History
Your execution history shows past workflow runs, logs, and results. How long this history is kept depends on your plan:| Plan | History Kept |
|---|---|
| Free | 1 day |
| Pro | 7 days |
| Team | 30 days |
Workflow Runtime
Maximum Runtime: 30 minutes
All workflows will automatically stop after 30 minutes to prevent runaway processes.UI Connection: 13 minutes
Important: When running a workflow manually from the UI, the live tracking connection may close after 13 minutes. What does this mean?- You won’t see live updates after 13 minutes
- Your workflow continues running in the background
- Check your execution history to see the final results and full logs
Frequently Asked Questions
I got "Resource limit exceeded. The data output from this node is too large" error
I got "Resource limit exceeded. The data output from this node is too large" error
This means a single node exceeded the 15 MB limit, or your total workflow exceeded 20 MB. Break your workflow into smaller pieces: split large data pulls across multiple workflows, use date ranges to get smaller chunks of data, and filter your reports to only essential metrics.
I can't see the history of my previous runs
I can't see the history of my previous runs
Check your plan’s execution history limit. Free plan only keeps 1 day of history, Pro plan keeps 7 days, and Team plan keeps 30 days. Upgrade your plan to keep history longer, or run your workflows more frequently to stay within the history window.
My workflow stopped tracking after 13 minutes but I need to see if it finished.
My workflow stopped tracking after 13 minutes but I need to see if it finished.
This is normal for longer workflows. The UI connection times out, but your workflow keeps running. Go to your Run History tab, click on the workflow that was running, and check the Execution History to see if it completed and view the detailed logs.
Why did my workflow stop at exactly 30 minutes?
Why did my workflow stop at exactly 30 minutes?
Workflows have a 30-minute maximum runtime for system stability. If you need longer processing, break complex workflows into smaller steps, use multiple workflows that run in sequence, or contact support if you have a specific use case.
I'm getting errors about data limits, but my reports don't seem that big.
I'm getting errors about data limits, but my reports don't seem that big.
Data limits include all the formatting and metadata, not just the visible numbers. Large date ranges create more data than expected, multiple metrics and dimensions add up quickly, and images and files count toward the 15 MB node limit. Try reducing your date range or selecting fewer metrics per workflow.
Do failed workflows count toward my credit usage?
Do failed workflows count toward my credit usage?
No. Only successful nodes consume credits. If a node fails due to data limits, no credit is charged for that node. Other successful nodes in the same workflow will still be charged. Manual workflow runs from the UI are always free regardless of success or failure.