Trace Scheduler Configurations
Overview
SAP Cloud Integration turns iFlow tracing off automatically after a short period, so keeping it on means re-enabling it by hand over and over. The Trace Scheduler Configurations page lets you set up reusable configurations that do this for you.
This matters because Int4 Suite builds tests by capturing real messages and replaying them — and on SAP Cloud Integration, messages are kept only while the iFlow's trace is active. A message processed with tracing off is never captured, leaving nothing for a crawler to turn into a test case. Keeping traces on is therefore the precondition for downstream capture, and the auto-stop guard switches the configuration off once you have collected enough.
A trace scheduler configuration describes what to keep traced and where: a name, a target SAP Cloud Integration system, the list of iFlows to keep tracing on, and optional safety limits. Once a configuration exists you can run it on demand or attach a recurring schedule to it. Each time it runs it walks through the listed iFlows and re-enables trace logging on each one, and records the outcome as a run you can review afterwards.
A configuration can also include an auto-stop guard: pick a folder and a test-case count, and the configuration will switch itself off once that folder reaches the chosen number of test cases. This stops traces from being left on indefinitely after you have collected everything you need.
This page is the list of all the trace scheduler configurations you are allowed to see. From here you can search the list, open a configuration to inspect or edit it, start creating a new one, and export the list. Creating and editing the configuration itself — choosing the system, adding iFlows, setting limits, and managing the schedule — happens on the configuration's own page, which opens when you create a new configuration or click an existing one.
This feature only works with SAP Cloud Integration systems.
Tasks
How to start a new configuration
- Click Create New at the left of the toolbar.
- You are taken to a blank configuration page. Fill in the name, pick the SAP Cloud Integration system, add the iFlows you want to keep traced, and — if you want — set an auto-stop limit and a schedule. The configuration is saved from that page.
The Create New button is disabled if you do not have permission to create trace scheduler configurations.
Field reference
| Column | Description |
|---|---|
| Name | The configuration's unique label. Click it to open the configuration. |
| Description | An optional short note describing the configuration. |
| System Under Test | The SAP Cloud Integration system whose iFlows this configuration keeps traced. |
| Active | Whether the configuration currently accepts runs. The auto-stop guard turns this off automatically once the chosen test-case limit is reached; you can turn it back on after raising the limit. |
| Scheduled | Whether a recurring schedule is attached and enabled for this configuration. |
| Test Run | Whether the configuration runs in test mode. In test mode a run only counts the iFlows it would have traced, without actually contacting SAP Cloud Integration — useful for checking a configuration before letting it touch a live system. |
| Last Run | When this configuration last ran, shown as a relative time (hover for the exact timestamp). Empty if it has never run. |
| Created By | The user who created the configuration. |
| Created Date | When the configuration was created, shown as a relative time (hover for the exact timestamp). |
Tips & edge cases
- Traces are what makes the messages capturable. A crawer can only build test cases from messages the platform retained, and on SAP Cloud Integration those messages exist only for iFlows that were being traced while they ran. Enable the relevant iFlows here before you crawl, not after — once a message has been processed with tracing off, it cannot be recovered.
- Only SAP Cloud Integration is supported. A trace scheduler configuration can only target a SAP Cloud Integration system. Other system types are rejected when you try to save the configuration.
- Test mode is the default safety net. New configurations run in test mode, which simulates the work instead of contacting the live system. Switch test mode off (on the configuration page) only once you are confident the right iFlows are listed.
- The auto-stop guard can switch a configuration off on its own. When you set both an auto-stop folder and a test-case count, the configuration deactivates itself — and disables its schedule — the moment that folder reaches the count. The Active column will then read as inactive. Raise (or remove) the limit and reactivate it to resume scheduled runs.
- The auto-stop count can be slightly behind. The folder's test-case count is read from a periodically refreshed summary, so a run started immediately after importing a batch of test cases may still use the previous count.
- Manual runs ignore the active flag. Even after the auto-stop guard has deactivated a configuration, you can still run it by hand from its own page; only the recurring schedule stops firing. Scheduled runs do respect the active flag.
- Runs cannot be cancelled. Once a run has started there is no way to abort it — you can only wait for it to finish.
- A configuration with a run in progress cannot be deleted. If a run is queued or still running, deletion is refused until it finishes.
- Configurations are edited in place — there is no version history. Unlike test cases, a trace scheduler configuration does not keep previous versions. Changes are recorded in the change log, but rolling back is a manual exercise.
- Schedules have a single owner. A schedule runs with its owner's permissions. If the owner loses the right to run the configuration (or is removed), scheduled runs stop until an administrator re-assigns the schedule to someone who can run it.
Related features
Prerequisites & permissions
About permissions. Int4 Suite controls what you can see and do through roles and permission groups assigned to your user. Each role grants permissions on a specific resource (for example, Test Case, Automation Object, System Under Test) at one of four levels: Read, Write, Delete, or Execute. Some permissions are further narrowed by project scope, so you may have access to one part of the system but not another.
If a button is disabled or a list comes back empty, missing permissions are the most likely cause. Ask an administrator to review your role assignments, or check IAM → Users if you have the User: Read permission.
To see this list you need the Trace Config: Read permission on the project scopes that contain the configurations. Additional permissions unlock specific actions:
- Trace Config: Write — required to create a new configuration (the Create New button) and to edit an existing one. Creating or editing also requires System Under Test: Execute on the chosen SAP Cloud Integration system, and — when an auto-stop folder is set — Folder: Write on that folder.
- Trace Config: Execute — required to run a configuration by hand (from its own page). The same system and folder permissions above also apply to running it.
- Trace Config Schedule: Write — required to create or change a recurring schedule, on top of the permissions needed to run the configuration. Only the schedule's owner can change it, unless you also have Trace Config Schedule: Change Owner.
- Trace Config: Delete — required to delete a configuration.
If a button is disabled and you believe your role should allow the action, missing permissions on the configuration, the system, or the auto-stop folder are the most likely cause.