You are here:
Developer Edition Limits and Guidelines for Data 360
Developer Edition orgs with Agentforce and Data 360 have certain limits and guidelines for Data 360 usage.
Required Editions
| Available in: Developer Edition |
This table is a partial list of limits. For other feature limits and guidelines related to Agentforce in Developer Edition orgs, see Developer Edition with Agentforce and Data 360. For Developer Edition org allocations, see Salesforce Developer Edition Allocations.
| Feature | Limits and Guidelines | Notes |
|---|---|---|
| Number of data spaces | 1 | The default data space is the only data space available. |
| Total data size limit | 10 GB | |
| Total number of data models | 300 | |
| Total number of data streams | 100 | |
| Total number of data lake objects (DLOs) | 100 | This limit applies to data lake objects created as part of data streams or in a standalone manner. |
| Total number of streaming data transforms per org | 3 | |
| Maximum number of batch transforms that can be created in an org | 5 | |
| Maximum number of data model objects | 300 | |
| Maximum scheduled job frequency per ruleset | 0 | When using Data 360 in a Developer Edition org, ruleset runs aren’t scheduled. Use Run Ruleset to kick off a ruleset job manually. |
| Total number of calculated insights per org | 10 | This limit includes calculated insights in active, inactive, and draft statuses. |
| How often calculated insights are processed | 0 | When using Data 360 in a Developer Edition org, schedules are ignored. Use Publish Now to kick off a refresh manually. |
| Total number of active segments | 25 | An active segment is a created segment with all functionality available. These limits are enforced by the UI. Learn more in Create a Standard Segment and Segment Types and Statuses. |
| Maximum number of scheduled publishes per standard segment per day | 0 | When using Data 360 in a Developer Edition org, segment publishes aren’t scheduled. Use Publish Now to kick off publication manually. |
| Total number of activation targets | 15 | An activation target is information stored for a given activation platform, which is where a segment’s data is sent during the activation process. |
| Total number of identity resolution rulesets per org | 2 | |
| Total number of data actions per org | 5 | |
| Total number of queries per day | 1,000, with 2 concurrent queries allowed | |
| Maximum number of scheduled refreshes per data stream per day | 0 | When using Data 360 in a Developer Edition org, data stream refreshes aren’t scheduled. Use Refresh Now to kick off data ingestion manually. |
Did this article solve your issue?
Let us know so we can improve!
