Skip to main content

​
Overview

Connection collection settings define default behavior for all resources within a connection. Individual resources can override these defaults with their own settings.
Collection settings apply to all resources in the connection unless overridden at the resource level.

​
Accessing Collection Settings

1

Navigate to Connection

Click on a connection to view its Resources page
2

Open Settings

Click the Settings icon (gear) in the Collection section
3

Configure in Modal

The Collection Settings modal opens

​
Schedule Configuration

Choose how and when resources in this connection collect data.

​
Interval-Based Scheduling

Resources collect on regular time intervals or at specific times. Options:
  • Specific times: “Daily at 2:00 AM”, “Weekly on Sunday at 3:00 PM”
  • Regular intervals: “Every 6 hours”, “Every 30 minutes”
Use interval scheduling for most use cases - it’s simple and reliable.

​
Timing: Static vs Rolling

For schedules that run more than once a day (for example every 2 hours or every 30 minutes), you can choose how each run is timed:
The next collection is scheduled for one full interval after the previous one finishes. This is simple and reliable, but the exact run time drifts depending on how long each collection takes.Example: an “every 2 hours” collection that starts at 1:00 and takes 5 minutes finishes at 1:05. The next run is scheduled 2 hours after it finished — so it starts at 3:05 (not 3:00), finishes at 3:10, and the following run starts at 5:10, and so on. Each run drifts a little later by however long the previous one took.
When you choose Static, set a Start time — the time of day the schedule is anchored to, shown in your instance’s timezone. Daylight saving is handled automatically, so runs stay at the same local time year-round.
The Timing option only appears for sub-daily schedules (hourly or minute-level intervals). Schedules that run daily or less often already fire at a specific time of day, so there is nothing to anchor.
Choose Static when you need predictable, evenly-spaced runs (for example “every 2 hours on the dot”). Rolling is fine for most cases.

​
Collection Profile

Control collection speed to manage load on your source systems. Information can be found in the Throttle Profile documentation.
Profile settings affect API rate limiting and database query batching but don’t change schedules.

​
Active Status

Enable or disable collection for the entire connection. Active (Toggle ON):
  • Resources collect according to their schedules
  • Discovery runs automatically every 3 hours
  • Normal operation
Inactive (Toggle OFF):
  • All data collection paused
  • Discovery still runs but no data is collected
  • Use for temporary suspension (e.g., maintenance windows)
Setting a connection to Inactive stops ALL resource collection, even if individual resources are enabled.

​
Saving Settings

After making changes:
1

Review Changes

Verify all settings are correct
2

Click Save

Click the Save button at the bottom of the modal
3

Confirm Application

Settings apply immediately to the connection and all resources using defaults

​
How Settings Apply to Resources

​
Default Behavior

Resources without their own collection settings inherit from the connection:

​
Resource Overrides

Individual resources can override:
  • ✅ Schedule (intervals)
  • ✅ Active status (if connection is active)
  • ❌ Collection profile (always inherits from connection)
See Resource Collection Settings to configure resource-specific overrides.

​
Best Practices

Start with Interval Scheduling

Use simple interval schedules until you need more complex scheduling

Schedule During Off-Peak Hours

Set collection times when your source systems have low activity

Use Standard Profile First

Only change to High or Low if you have specific performance needs

Test Schedule Changes

Monitor the first few collections after changing schedules to verify timing

​
Common Scenarios

​
Scenario: Daily Overnight Collection

Goal: Collect all connection data once per day at 2:00 AM Configuration:
  • Schedule Type: Interval
  • Schedule: “Daily at 2:00 AM”
  • Profile: Standard
  • Active: ON

​
Scenario: Frequent Real-Time Updates

Goal: Keep data as current as possible with hourly updates Configuration:
  • Schedule Type: Interval
  • Schedule: “Every 1 hour”
  • Profile: High (for maximum speed)
  • Active: ON

​
Scenario: Maintenance Window

Goal: Temporarily pause collection during source system maintenance Configuration:
  • Active: OFF
  • (Keep all other settings unchanged)
  • Re-enable Active when maintenance completes

​
Troubleshooting

​
Settings Not Applying

Symptoms: Changes saved but collection behavior doesn’t change Possible causes:
  • Resources have overriding settings
  • Connection is inactive
  • Schedule hasn’t triggered yet
Resolution:
  1. Check individual resource settings for overrides
  2. Verify connection Active status is ON
  3. Wait for next scheduled time or trigger manual collection

​

Resource Collection Settings

Override connection defaults for specific resources

Monitoring Jobs

Track collection execution and verify schedules

Troubleshooting

Resolve collection issues