Known issues in Splunk Business Flow
Splunk Business Flow has the following reported known issues and workarounds.
4/15/20 release
Date filed
|
Issue number
|
Description
|
2020-04-16 |
FLOW-3581 |
Multiple correlation Ids does not load Validate tab in Flow Model
|
2020-04-16 |
FLOW-3583 |
Loading some Flows with custom numeric attributes isn't working
|
2020-04-15 |
FLOW-3575 |
Journey Duration filter panel bin slider not working
|
2020-04-14 |
FLOW-3566 |
sort by repetitions on list view crashes / errors list view
|
2020-04-09 |
FLOW-3536 |
Dragging flowchart nodes quickly can nodes to move to previous positions
|
2.0.0. Release
4/1/20 release
Date filed
|
Issue number
|
Description
|
2020-04-01 |
FLOW-3469 |
Setting Flow Models to Private labels dependent Flows as <encrypted item>. Workaround: Set Flow Model to Shared
|
3/4/20 release
Date filed
|
Issue number
|
Description
|
2020-02-07 |
FLOW-3074 |
Notification condition still persists when Filter Set is deleted
|
2/5/20 release
Date filed
|
Issue number
|
Description
|
2020-02-24 |
FLOW-3141 |
Changing the "mode" in a Flow also changes it in the Flow Model and any other Flows built off the Flow Model
|
2020-01-23 |
FLOW-2974 |
Can't delete a license.
|
9/4/19 release
Date filed
|
Issue number
|
Description
|
2019-07-29 |
FLOW-1987 |
Unable to import saved searches, data models, table datasets
|
8/21/19 release
Date filed
|
Issue number
|
Description
|
2019-08-22 |
FLOW-2124 |
Adding second occurrence filter when the first occurrence filter is empty results in error.
|
2019-08-21 |
FLOW-2113 |
Flowchart for A in AB mode is not centered. Workaround: zoom out on browser and click "reset layout" in Flowchart.
|
7/24/19 release
Date filed
|
Issue number
|
Description
|
2019-07-29 |
FLOW-1987 |
Unable to import saved searches, data models, table datasets
|
There aren't any known issues in the 7/24/19 release.
6/26/19 release
There aren't any known issues in the 6/26/19 release.
6/12/19 release
Date filed
|
Issue number
|
Description
|
2019-06-06 |
FLOW-1708 |
The following error might occur if you imported data with timestamps in the future: "Error in 'journeytotree' command: (ValueError) No JSON object could be decoded."
|
2019-04-05 |
FLOW-1386 |
Timestamps in the app might show a time in the future if the server time zone is not the same as the browser's.
|
5/29/19 release
Date filed
|
Issue number
|
Description
|
2019-08-22 |
FLOW-2122 |
JavaScript error in take focus coming from Toast Messages
|
2019-06-10 |
FLOW-1726 |
Incorrect Number of Pagination pages
|
2019-04-16 |
FLOW-1440 |
Combining Flow Models that contain the same Attribute field name results in an error.
|
2019-04-04 |
FLOW-1373 |
If your data sources contain more than 100 Attribute fields some fields might not appear in the Flow Model editor.
|
5/15/19 release
Date filed
|
Issue number
|
Description
|
2019-05-13 |
FLOW-1565 |
SBF does not work with a free license.
|
Workarounds
Known issue
|
Workaround
|
If there are more than 1000 steps you may experience performance issues.
|
Reduce the number of steps.
|
Risky search command
|
The following commands are not compatible with search in Splunk Business Flow. Use a different search command.
crawl
createrss
delete
dispatch
dump
input
internalinputcsv
outputcsv
outputlookup
rest
runshellscript
script
sendemail
stash
tagcreate
tagdelete
tscollect
|
The _time field in an inputlook is not extracted at index time.
|
The events are assigned a timestamp from the time of ingestion into Splunk. For more information, see How Splunk extracts timestamps in the Splunk Enterprise Getting Data In Manual.
|
Feedback submitted, thanks!