Crawler Runs
LicenseInt4 Shield Lite (1 of 3) · Custom add-on (2)Details
| Feature or limit | Int4 Shield Lite |
|---|---|
| SAP PI/PO crawler | Included |
| SAP Integration Suite crawler | Add-on |
| Business object crawler | Add-on |
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
A crawler discovers real messages on your integration platform — or documents behind a Business Object — over a chosen time window and turns them into test cases. Every time a crawler configuration is started, by hand or on its schedule, it records a run.
A run is the bulk authoring step in action: in one pass the robot searches for historical messages that match the configuration, then creates a test case from each suitable message and files it into the target folder. This page is where you check that the pass did what you expected — how much traffic was found in the window, how much of it became test cases, and how much was set aside. Reviewing runs is how you build confidence in a configuration before you let it run on a schedule and grow a regression suite on its own.
The list shows one row per run, newest first. It is read-only: you start, schedule and change crawls from the crawler configuration, not here. Open a run to see its totals, its details and its log, which update live while the run is in progress.
A run moves through Pending and Running and ends as Completed or Failed. Runs started in preview (test run) mode are marked as such: they only report what they found and never create test cases.
Tasks
How to narrow the list
- Type part of a configuration name or description into Search by config name....
- Use the status and platform drop-downs to show, for example, only failed runs or only SAP Cloud Integration runs.
- Click Only mine to keep only the runs you started, including the scheduled runs of schedules you own.
- Click Clear filters to reset everything.
The filters are kept in the page address, so you can bookmark or share a filtered view. The Dashboard links to this page with Only mine already applied.
How to review a run
- Click the configuration name, or anywhere on the row.
- The run page shows the totals at the top — Messages Found, Test Cases Created, Test Cases Skipped and Errors — followed by Details (platform, test run mode, job ID, status and run ID) and Run Logs.
- Read the log to see what happened per automation object: how many messages were found, how many test cases were created or skipped, and any warning or error. Pick a level in the level drop-down to see only entries of that level and above — Warning, for example, shows warnings and errors.
While a run is pending or running, the totals, status and log refresh on their own. Use the copy button next to the run ID when you need to quote the run to a colleague or to support.
How to export the run history
- Apply the filters you want.
- Click the export button at the right of the toolbar and choose Excel or PDF. The file is named crawler-runs plus a timestamp.
The export contains the rows loaded into the list so far; scroll down to load more before exporting a long history.
Field reference
Each row summarises one run. The figures are totals over every automation object the run covered.
| Column | Description |
|---|---|
| Configuration | The crawler configuration that ran. Empty if the configuration has since been deleted. |
| Status | Pending (queued), Running, Completed (no automation object failed), or Failed (at least one automation object failed). |
| Started | When the run was started. |
| Created | How many test cases the run created. Always zero in preview mode. |
| Errors | How many automation objects of the run failed. Any value above zero marks the run as failed. |
| Messages | How many messages (or documents) matched the configuration in the time window, after any filters. |
| Platform | Where the crawler read from — SAP PI/PO, SAP Cloud Integration, SAP CI Trading Partner Management or Business Objects. |
| Skipped | How many found messages did not become test cases: duplicates, messages beyond the folder limit, and messages that could not be captured. In preview mode, every found message counts as skipped. |
| Completed | When the run finished. Empty while it is pending or running. |
| Test Run | Whether the run was a preview that only counted messages. |
The columns are listed in the order the list drops them when the window gets narrow: the last ones disappear first. Widen the window to see them again.
Tips & edge cases
- Previews never create test cases. A preview run reports every matching message as found and as skipped, and creates nothing. Duplicate checks and the folder limit are only applied by a real run, so expect a real run to create fewer test cases than the preview found.
- A high skipped count is usually expected. It reflects duplicate filtering and the folder limit, not a problem with the crawl. Once the target folder is full, later runs skip everything.
- Failed means at least one automation object failed. The other automation objects of the run may still have created test cases. The log names the automation object that failed and why — for example an empty custom header filter, a missing date parameter, or a connection problem.
- A low found count usually means the window came up empty. A crawl reads historical messages, so few or no messages often point at the time window or at the platform not having kept them. For SAP Cloud Integration, check that tracing was on for those iFlows during the window.
- Watch for ceiling warnings. An SAP Cloud Integration item or a Business Object list reads at most 10,000 messages or documents per run; the log warns when that ceiling was reached and the window should be narrowed.
- Runs cannot be cancelled. A run always finishes on its own.
- Deleted configurations. When a configuration is deleted, its past runs stay in the list with an empty configuration name.
- Empty list. No crawler runs found can simply mean nothing has run yet, or that your filters exclude every run.
- Opening a run needs access to its configuration's project scope. The list shows all runs, but you can open only those whose configuration is in a project scope where you may read crawlers.
Related features
- Crawler Configurations — where crawls are defined, scheduled and started.
- Trace scheduler runs — when traces were switched on for SAP Cloud Integration crawls.
- Dashboard — crawler runs of the last 24 hours and your own latest runs.
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 view this page you need the Crawler: Read permission. Opening a run additionally needs it in the project scope of the run's configuration.