Skip to main content

​
Overview

Enabling resources activates data collection for specific tables, views, or endpoints. Only enabled resources collect data according to their configured schedules.
New resources discovered automatically default to Inactive status. You must explicitly enable them to begin collection.

​
How Resource Enabling Works

When you enable a resource:
  1. The resource toggle turns ON (green)
  2. Changes are staged (not yet saved)
  3. Click Save to apply and begin collection
  4. The resource starts collecting according to its schedule

​
Enabling Single Resources

1

Locate Resource

Find the resource in the Resources table
2

Click Toggle

Click the toggle switch in the first columnThe toggle turns green (ON)
3

Save Changes

Click the Save button in the floating save bar
Changes are not applied until you click Save. You can toggle multiple resources before saving.
4

Verify Activation

The resource is now active and will collect on its next scheduled time

​
Enabling Multiple Resources

You can enable several resources at once before saving:
1

Toggle Multiple Resources

Click the toggle for each resource you want to enableThe floating save bar shows how many resources have pending changes
2

Review Staged Changes

Check the save bar to confirm the count
3

Save All Changes

Click Save to activate all toggled resources at once
Batch enabling is efficient when setting up a new connection - enable all needed resources, then save once.

​
Disabling Resources

The same process works in reverse to disable collection:
1

Click Toggle to OFF

Click the blue toggle to turn it gray (OFF)
2

Save Changes

Click Save in the floating bar
3

Collection Stops

The resource stops collecting data
  • Scheduled jobs are canceled
  • Existing data in lakehouse is preserved
Disabling a resource stops all future collections. Historical data remains but no new data is collected.

​
Canceling Changes

To discard toggled changes before saving:
1

Click Cancel

Click Cancel in the floating save bar
2

Changes Reverted

All toggles return to their saved state

​
Access Control Requirements

Some resources cannot be enabled without access control configuration: Indicators:
  • Lock icon next to resource name
  • Toggle is disabled (grayed out)
  • Tooltip explains access control requirement
Resolution:
  1. Configure access control for the resource
  2. See Access Control documentation
  3. Return to enable the resource once access control is set
Access control ensures only authorized users can query this resource’s data in your lakehouse.

​
Connection-Level Impact

Remember that connection status affects all resources:
Connection StatusResource Toggle ONWill Resource Collect?
ActiveYes✅ Yes
ActiveNo❌ No
InactiveYes❌ No - Connection paused
InactiveNo❌ No
Even if a resource is enabled, it won’t collect if the connection is set to Inactive.

​
First Collection After Enabling

When you first enable a resource:
1

Wait for Scheduled Time

Collection starts at the next scheduled interval
  • Connection schedule (if resource uses default)
  • Resource schedule (if custom override configured)
2

Or Trigger Manually

Don’t want to wait? Trigger a manual collection:
3

Monitor First Job

Watch the first collection to verify:
  • Authentication works
  • Data is accessible
  • No configuration errors
After enabling critical resources, trigger a manual collection to verify they work immediately rather than waiting for the schedule.

​
Common Workflows

​
Initial Setup: Enable Core Tables

After creating a connection:
1

Review All Resources

Browse the discovered resources list
2

Identify Critical Data

Determine which tables/endpoints contain needed data
3

Enable Core Resources

Toggle ON the essential resources first (customers, products, transactions)
4

Save and Test

Save changes and trigger manual collection to test
5

Enable Additional Resources

After core resources work, enable supplementary data

​
Temporary Pause: Disable During Maintenance

To temporarily stop collection:
1

Disable Affected Resources

Toggle OFF resources undergoing maintenance
2

Save Changes

Apply the changes
3

Perform Maintenance

Complete source system work
4

Re-enable Resources

Toggle back ON and save
For connection-wide pauses, set the connection to Inactive instead of disabling individual resources.

​
Best Practices

Start Small

Enable a few critical resources first, verify they work, then expand

Test Before Production

Enable and test in a development connection before production

Document Decisions

Keep notes on why certain resources are enabled or disabled

Review Periodically

Regularly review enabled resources to ensure they’re still needed

​
Troubleshooting

​
Toggle Won’t Turn On

Symptoms: Click toggle but it doesn’t change Possible causes:
  • Access control required
  • Network issue
  • Browser cache problem
Resolution:
  1. Check for lock icon (access control required)
  2. Refresh the page and try again
  3. Check browser console for errors

​
Changes Not Saving

Symptoms: Click Save but resources don’t activate Possible causes:
  • Network interruption
  • Server error
  • Validation failure
Resolution:
  1. Check for error messages
  2. Refresh page and check resource status
  3. Try enabling fewer resources at once
  4. Contact support if issue persists

​
Resource Enabled But Not Collecting

Symptoms: Resource is active but no jobs appear Possible causes:
  • Connection is inactive
  • Schedule hasn’t triggered yet
Resolution:
  1. Verify connection status is Active
  2. Check schedule timing
  3. Trigger manual collection to test
  4. See Troubleshooting

​
Next Steps

Collection Settings

Configure schedules and load types for enabled resources

Triggering Collection

Manually start collection for testing

Monitoring Jobs

Track collection execution and performance

Troubleshooting

Resolve resource collection issues