Queues project files for the submission pipeline and captures outcome events (pass-qc, not-pass-qc) after pipeline completion. Intended to be triggered by the form-screening gear.
The form-scheduler captures outcome events after pipeline completion:
Submit events are handled separately by the identifier-lookup gear. For detailed event capture documentation, see the gear-specific event logging guide.
This gear takes the following configuration parameters:
| Parameter | Default | Description |
|---|---|---|
source_email |
"nacchelp@uw.edu" |
Source email address to send completion notifications from. If empty, emails will not be sent. |
portal_url_path |
"/prod/flywheel/portal" |
Parameter path for the portal URL used in email notifications. |
apikey_path_prefix |
"/prod/flywheel/gearbot" |
The instance-specific AWS parameter path prefix for API key. |
event_bucket |
"submission-events" |
S3 bucket name for visit event capture. The gear must have write access to this bucket. |
event_environment |
"prod" |
Environment for event capture. Valid values are “prod” or “dev”. This determines the environment prefix used when storing events in S3. |
This gear requires the following input files:
| Input | Description |
|---|---|
pipeline_configs_file |
A JSON file with pipeline configurations defining the submission pipeline stages and their settings. |
form_configs_file |
A JSON file with form module configurations for validation and processing. |
This gear currently does not support a dry-run mode.