Job Scheduling

Scheduling overview

Jobs can be scheduled or run manually. Scheduling behavior depends on your plan.

• Free plan limits: typically one manual scheduled run per day and limited concurrent processing.
• Active jobs: All active jobs are queued; processing often happens one-by-one though multiple jobs can run in parallel depending on available agents and plan.

Manual schedule

• Free plan: manual schedules are restricted (e.g., once per day). Upgrade plan to increase frequency and concurrency.

What is an Agent

• Agent: a service that picks up work for local or enterprise processing. Agents can be installed as Docker containers or run as system services.
• Creating agent: deploy the Docker image, configure environment variables (see Enterprise Agent Configuration), and register the agent with your DeDuplica tenant.
• Restarting agent: when restarting, decide whether to purge the local queue. Purging removes pending messages; often you should NOT purge unless you want to drop queued work.

Enterprise agent

• Runs in client network, processes data locally, and can use encrypted storage. It supports webhooks and dynamics calls without disclosing connection details to DeDuplica cloud.
• Requires a client-side Azure Storage account for message exchange and a license key.

Enterprise agent configuration

• Provide environment variables: storage connection string, agent ID, license key, and any connection-specific credentials.
• Install via Docker image. Ensure the container has internet access to pull messages and apply updates; translation agent mapping is required on the DeDuplica cloud side.

Job Executions

• Navigate to the Job Executions view to see run history, status, and logs. Use filters to find specific runs and inspect detailed logs for troubleshooting.