Trace Scheduler Runs
LicenseIncluded in Int4 Shield LiteDetails
| Feature or limit | Int4 Shield Lite |
|---|---|
| SAP Integration Suite testing | Included |
Anything a license model does not include can be added through a custom license. The license installed for you is shown in the app under Profile → License. All features by license
Overview
Every time a trace scheduler configuration runs — started by hand, fired by its schedule, or triggered by a crawler that manages its own traces — Int4 Suite records a run. A run walks the configuration's enabled iFlows, re-enables trace logging on each, and stores the outcome per iFlow.
This page is the history of those runs, newest first. Use it to confirm that traces were really switched on before you crawl, to find iFlows that keep failing, and to see when a configuration stopped itself because its auto-stop limit was reached. The list is read-only; runs are started from the configuration page.
Open a run to see its details: the counts of enabled and failed iFlows, the result for each iFlow with any error text, and the run log. While a run is still pending or running, its detail page updates by itself.
Tasks
How to find runs
- Type part of a configuration name in Search by config name.... The search also matches configuration descriptions.
- Use the status drop-down to show only Pending, Running, Completed, or Failed runs.
- Click Clear filters to reset both.
How to check why iFlows failed
- Open the run from the list.
- Check the iFlows Failed count at the top.
- In iFlow Results, find the rows with status
failedand read the Error column. Expand a row to read a long or multi-line error in full. - Read Run Logs for the step-by-step log of the run.
Typical causes are an iFlow ID that is not deployed on the tenant, or a connection or authorization problem with the system under test.
How to export the run history
- Filter the list as needed.
- Click the export button at the right of the toolbar and choose Excel or PDF. The file is named trace-scheduler-runs and contains the loaded rows.
Field reference
List columns
Depending on the window width, lower-priority columns are hidden first.
| Column | Description |
|---|---|
| Configuration | The configuration that ran. Click it, or the row, to open the run. Runs triggered by a crawler's automatic trace management show the crawler name with the prefix [crawler]. Empty when the configuration has since been deleted. |
| Status | Pending (queued), Running, Completed (no iFlow failed), or Failed (at least one iFlow failed, or the configuration no longer existed when the run started). |
| Started | When the run was created, as a relative time. |
| iFlows Enabled | How many iFlows had their trace re-enabled. In a test run, how many would have been. |
| iFlows Failed | How many iFlows could not have their trace enabled. |
| Limit Reached | Yes when the auto-stop guard fired: the watched folder had reached its test-case limit, so the run enabled no traces and the configuration switched itself off. |
| Completed | When the run finished. Empty while it is pending or running. |
| Test Run | Whether the run was simulated without contacting SAP Cloud Integration. Reflects the configuration's setting when the run was started. |
Run detail
| Element | Description |
|---|---|
| iFlows Enabled / iFlows Failed | The run's totals, as in the list. |
| Test Run Mode | Whether the run was a test run. |
| Job ID | The identifier of the background job that processed the run. Useful when reporting a problem. |
| Limit Reached | Whether the auto-stop guard fired. |
| Status | The run's status. |
| Run ID | The run's unique identifier. |
| Created At, Started At, Completed At | When the run was queued, started processing, and finished. |
| Error Message: | Shown when iFlows failed (for example "2 iflow(s) failed to enable trace") or when the configuration no longer existed. |
| iFlow Results | One row per processed iFlow: iFlow ID, Status (ok or failed) and Error. A test run shows a single row test_run with status simulated. Not shown when the auto-stop guard fired. |
| Run Logs | The run's log messages. |
Tips & edge cases
- "Completed" does not always mean traces were enabled. A run stopped by the auto-stop guard finishes as Completed with no iFlows enabled. Check Limit Reached.
- A failed iFlow means missing messages. While an iFlow's trace is off, its messages are not captured, so a later crawl finds nothing for that period. Fix repeated failures before relying on a crawl.
- Test runs change nothing on the tenant. They only count the enabled iFlows.
- Crawler runs appear here too. A scheduled crawler with Automatically manage trace switched on triggers a run about every nine minutes during the hour before each scheduled crawl. Search for
[crawler]to find them. - Runs of deleted configurations stay in the list with an empty configuration name, but their details can no longer be opened.
- Runs cannot be cancelled. A started run always runs to the end; the status Cancelled is not used.
Related features
- Trace Scheduler Configurations — create, schedule and run the configurations.
- Crawlers — turn traced messages into test cases.
Prerequisites & permissions
About permissions. What you can see and do is decided by the roles assigned to your user. Each role bundles permission groups, and each permission group allows activities — Read, Write, Delete, Execute and, for schedules, Change owner — on a kind of record (for example Test Case, Automation Object, System Under Test). A role grants its groups per project scope, so you may be allowed to change records in one project but only view, or not see, those of another.
If a button is disabled, a page says you don't have access, or a list comes back empty, missing permissions are the most likely cause — or, for whole product areas, the installed licence. You can review your own access under Profile → My access; an administrator can change your roles under IAM → Users.
To open this page you need Trace Configuration: Read. The list shows runs of all configurations; opening a run also requires that permission for the project scope of the run's configuration.