V-Spark Online Help

Maintenance Updates Since the Initial 3.5.0 Release

This section identifies fixes that were introduced in patch releases and hot fixes since the initial 3.5.0 release, and are therefore now included in the latest version of the 3.5.0 release. Maintenance versions and associated fixes are listed most recent to earliest:

  1. Improved response handling for systems using V‑Cloud. Eliminated extraneous 503 errors generated when communicating with V‑Cloud to minimize unnecessary noise in Job Manager log files. (3.5.1-5)

  2. Backend V‑Spark services now properly stop when Redis is down - Prior to this change, stopping the backend service while Redis was down could lead to errors that required killing backend processes manually in order to restart them. (3.5.1-4)

  3. Update to support the latest version of the Datatool - if your V‑Spark installation has a copy of the Datatool provided by the Voci support team, this release will add value by providing some core changes that enable the Datatool to exercise its sampling feature with V‑Spark 3.5.x releases. (3.5.1-4)

  4. Improved handling of hardware boot and reboot events - The V‑Spark initialization process was updated to permit V‑Spark services to start automatically during hardware boot and reboot. (3.5.1-3)

  5. Dashboard performance optimization - Loading optimization updates were made to allow all folder-level dashboard widgets to load faster. (3.5.1-3)

  6. Google Chrome 83 support update - Chrome 83 now blocks all downloads initiated from or instantiated in a sandboxed iframe by default. This update enables V‑Spark to override that default behavior and allow file downloads. (3.5.1-2)

  7. Failed file details in /request- The V‑Spark /request endpoint displays files that were unable to be transcribed. Details explaining why the files were not transcribed are included; for example, the file type was not supported or the file contained bad metadata. (3.5.0-17)

  8. Callback improvements- Callback status messages were improved to include more specific information about status codes and whether the callback failed or succeeded. (3.5.0-11)

  9. Delete files from V‑Spark- Transcript files can be deleted using the V‑Spark API or user interface. Deleted files will no longer be available in the file list /transcript view. However, summary data will not be updated to reflect deletion at this time. (3.5.0-10)