Troubleshooting Common Vulnerability Reporting Framework data import

  • Release version: Zurich
  • Updated July 31, 2025
  • 1 minute to read

    • Troubleshooting actions can help resolve common issues when importing CVRF data in the Vulnerability Response application.

    Issue Action
    Integration run duration is long If the integration runs for a longer period than expected, then do the following:
    1. Navigate to the sn_vul_ds_import_q_entry table.
    2. Group by the Status field. You can see the entries, which are in the Completed, In progress, or In queued states.
    Integration failed in API-based import If the integration fails in API-based import, do the following:
    1. Navigate to Flow Designer.
    2. Open the flow that was selected in the configuration.
      Note:
      In the case of Cisco, open the Advisory Parsing flow.
    3. Click Executions.
    4. Open the latest execution or the execution that must be debugged.
    5. Check the flow in each stage.
    Integration failed in API-based import with a timeout error If integration fails in an API-based import due to timeout in the advisory parsing flow, then do the following:
    1. Increase the timeout by opening sys_properties.LIST.
    2. In the Name column, search for sn_vul.CVRFFlowTimeout (inMiliSeconds).
      Note:
      Time is in milliseconds.
    3. Open the record and update the value with a large number.
    4. Save the record and rerun the integration.
    Integration failed with error 'Scanner mapping to vendor-mapping data transformation is in progress' Check if the integration fails during the URL or API-based import, with the following error:Scanner mapping to vendor-mapping data transformation is in progress. Data will be populated only after the transformation is completed. Try to execute after some time.

    If you have this error, then wait for some time and execute the integration again.
    Import queue not getting created during file import During a file import, sometimes the import queue does not get created. This failure means that the transformation that maps scanner-mapping data to vendor-mapping data is in progress. The queue entry is created once the process gets completed.