Feed Management

The Feed Management page is the operational control panel for background feed execution in Actualog. It lets administrators control whether the hosted feed worker runs, define how often the worker polls for work, and verify the current runtime state in one place.

Use this page to keep feed processing predictable across deployments and to safely pause or resume inbound data operations.

What feed management means in Actualog

In Actualog, a feed is a configured inbound or outbound integration source that delivers product, catalog, pricing, metadata, or related payloads into user workspace data.

Feed management is the runtime governance layer for that import pipeline:

  • it controls whether the background feed worker is allowed to execute,
  • it controls polling cadence for checking pending feed jobs,
  • it exposes startup defaults vs runtime overrides,
  • it shows the effective runtime state that truly governs execution.

This helps admins answer the most important operations question quickly:

“Are feeds running right now, and if not, why not?”

Open the Feed Management page

  1. Sign in with an administrator account.
  2. Open Admin → Services → Feed Management.
  3. Review Runtime controls and Feed worker status before making changes.

Runtime controls section

The Runtime controls card is where you stage configuration changes.

1) Enabled / Disabled switch

  • This switch sets the runtime override for feed worker execution.
  • Enabled means the runtime override allows the worker to process feeds.
  • Disabled means the runtime override blocks worker execution.

Important behavior:

  • The switch change is staged in the UI.
  • The backend setting is updated only after you click Save runtime settings.

2) Polling interval (seconds)

  • Defines how frequently the worker checks for pending feed work.
  • Allowed range is 5 to 3600 seconds.
  • Lower values give faster responsiveness but increase polling frequency.
  • Higher values reduce infrastructure noise but increase delay before new work starts.

Recommended tuning guidance:

  • Start with 60 seconds for balanced behavior.
  • Move lower only if near-real-time feed execution is required.
  • Move higher in low-volume environments to reduce unnecessary cycles.

3) Save runtime settings

  • Persists your staged runtime settings.
  • Stores the runtime override and interval in admin runtime settings.
  • Triggers status refresh so the right panel reflects the saved state.

Feed worker status section (field-by-field)

The Feed worker status card explains how final execution state is determined.

Runtime override stored

Indicates whether a persisted runtime override currently exists.

  • Stored: runtime override is present in settings.
  • If not stored, startup defaults are used directly.

Runtime enabled

Shows the boolean value of the persisted runtime override.

  • Enabled: override permits worker execution.
  • Disabled: override blocks worker execution.

Startup default

Represents the value loaded from environment startup configuration.

This is the baseline setting when no runtime override is present.

Effective runtime

Shows the final value used by the worker loop.

This is the most important status line for operations because it reflects the net result after applying startup default plus runtime override rules.

Polling interval

Shows the currently effective polling interval value used by the worker loop.

How Actualog admins should manage feeds day-to-day

Normal operations

  1. Keep runtime Enabled.
  2. Keep polling interval at an agreed baseline (commonly 60 seconds).
  3. Periodically confirm Effective runtime = Enabled after deployments.

Planned maintenance window

  1. Set runtime to Disabled.
  2. Save settings.
  3. Verify Effective runtime = Disabled.
  4. Perform maintenance.
  5. Re-enable runtime and save.
  6. Verify Effective runtime = Enabled.

Incident response (unexpected feed load or source instability)

  1. Disable runtime to stop new worker cycles.
  2. Coordinate with source/integration teams.
  3. Correct source payload or connectivity issues.
  4. Re-enable runtime after validation.
  5. Monitor first resumed cycles.

Operational interpretation tips

  • If Startup default = Enabled but Effective runtime = Disabled, a runtime override is currently disabling processing.
  • If Runtime override stored is absent and startup is disabled, feeds remain off until startup config changes.
  • If runtime is enabled but expected imports do not appear, investigate feed definitions, source availability, and feed-specific errors (outside this page).

Governance and ownership

Feed Management should be owned by platform or integration administrators who understand:

  • expected feed execution windows,
  • acceptable processing latency,
  • external source reliability,
  • downstream business impact of paused imports.

Apply the principle of least change:

  • change one setting at a time,
  • save,
  • verify status,
  • then continue with further tuning if required.

Best practices checklist

  • Verify worker status after each deployment.
  • Record runtime toggles in change-management notes.
  • Use maintenance procedures when pausing feeds.
  • Keep polling interval within approved operational bounds.
  • Reconfirm Effective runtime after every save action.

Summary

Feed Management in Actualog gives administrators precise runtime control over the feed worker. The page combines action controls (toggle + interval + save) with diagnostic status (override/startup/effective) so admins can confidently enable, pause, tune, and audit inbound feed processing.