Continuous screening
Continuous screening schedules recurring runs for a subject. It requires an active Enterprise subscription. The Daily interval additionally requires the Daily Continuous Screening add-on.
Set the interval at creation
Section titled “Set the interval at creation”Include continuousScreening in the create-subject request. Supported intervals are None, Monthly, SemiAnnual, Annual, Quarterly, and Daily. None leaves continuous screening disabled.
The NewSubjectContinuousScreening schema lists the available options. Confirm the appropriate interval and notification settings with Ferretly Integrations before enabling recurring runs.
Track recurring runs
Section titled “Track recurring runs”Keep the subject’s id and your externalSystemId for status callbacks and result requests. A recurring run can make the results endpoint temporarily unavailable while processing is active. Retrieve results after completion, then handle report availability separately.
Use webhooks to receive progress and completion updates. The Subject schema includes continuous-screening settings and dates such as previousRunDate and nextScreeningDate when available.
Follow your organization’s workflow
Section titled “Follow your organization’s workflow”Recurring runs are managed by their configured schedule. Follow the guidance for Analyst Assistance or without Analyst Assistance according to your organization’s service configuration.
Integration testing
Section titled “Integration testing”During your subject creation testing phase, don’t enable continuous screening unless you have isDebug set to true.