In normal operation, an active profile automatically starts as soon as its Input Agent receives data (time-driven or event-driven). The data is saved as a backup file and a job is created for the profile.

Additionally, there is the possibility to start a profile manually. This is the purpose of the restart dialogue. It can be opened here in the Control Center under "Logs/Overview" and also in the following places. See also system variable VAR_SYS_RESTART.

Via the context menu of a profile in the profile overview.
In a mapping test via the upper menu bar of a profile.

Settings

images/download/attachments/137299623/restart-version-1-modificationdate-1744265213723-api-v2.png

(1) Search period on top.

(2) Archive files shows all archive files of the profile for the selected period. Unresolved files shows the files from area "Unresolved". Note: This option can be suppressed if the user right "Unresolved files" is not assigned.

(3) List below: List of all archive files found for the profile (whose job was restarted). See context menu below.

(4) Do not create checkpoint: If this checkbox is set, the restarted job will not be considered for any defined checkpoints of the profile.

(5) Is test run: If this checkbox is set, the started job will be treated as a test run. That means that

the system variable VAR_IS_TEST is set to "true" (and VAR_IS_NOT_TEST to "false") (see also item 9) and
in phase 6, only those Responses are considered that have the checkbox "Only at test" set.

Note: Both items only apply for "Upload file" and not for "Start cron" (6). Button "Upload file" is only shown for profiles that have no time-driven Input Agent.

(6) Start cron: If the profile to be restarted has a time-driven Input Agent, it can be restarted with this button. Archive files are not taken into account. If a profile is to be restarted with one or more specific archive files (which creates new jobs), the context menu should be used (see below). If the profile to be restarted has an event-driven Input Agent, you can manually upload a file here and start a job. Note: If a profile with a time-driven Input Agent is not active, the Input Agent will be executed, but the inactive profile will not process the received data. If another profile has the same Input Agent and is active, this profile might be able to accept the data instead (see section Input Agents that are forced to receive all the data) or the data is stored in the "Unresolved" area. In this case, there will be an entry in the Control Center under "General messages".

(7) OFTP: For profiles with an Input Agent of type "OFTP", the fetching of files (pickup) can be started with another button (not available here).

Context menu

Start	A job can be restarted with its archive file. This will create a new job. Multiple lines can be selected and started. Note: If an error job is restarted and the new job is successful, the old error job disappears neither from the overview nor from the error list.
Start with test flag of backup file	This option does not use the setting from (5) but the corresponding setting from the "ENV" data (if there are any).
Upload files	Upload file and restart the job with it. Note: If an error job is restarted and the new job is successful, the old error job disappears neither from the overview nor from the error list.
Edit file	Edit the selected archive file and restart the job with it. Note: If an error job is restarted and the new job is successful, the old error job disappears neither from the overview nor from the error list.
Edit meta data	Opens an additional metadata editor in which you can view and edit existing variables from the metadata.
Save as	Self-explanatory.

Blacklists and whitelists for file extensions

See section Blacklist and whitelists for file extensions.