Hi @AstinSebastian  I have recently had to wait 4 weeks for my Splunkbase submissions to be reviewed, this is typically due to manual_checks, when I ran AppInspect against your app it looks like there are 2 manual checks to be done, such as: Security vulnerabilities Check for insecure HTTP calls in Python. MANUAL_CHECK: Possible insecure HTTP Connection. Match: requests.get Positional arguments, ["?"]; Keyword arguments, {"timeout": "?"} File: bin/wmi_exp.py Line Number: 38 MANUAL_CHECK: Possible insecure HTTP Connection. Match: requests.get Positional arguments, ["?"]; Keyword arguments, {"timeout": "?"} File: bin/wmi_exp051224_working.py Line Number: 23 This will get assigned to a Splunk Engineer who manually vets the code and then will either pass or fail it, you will get an email notification once this has been completed. Did you know that you have also included "wmi_exp051224_working.py" in your app within the /bin directory? This has a hard-coded windows path for a config_file variable passed to the system open() function, this might also cause a manual check, and potential failure due to hard-coded windows path which is not compatible with Cloud. Please let me know how you get on and consider accepting this answer or adding karma this answer if it has helped. Regards Will ... View more

You probably have looked this https://dev.splunk.com/enterprise/tutorials/module_setuppages/plansetup ? One place where you could look help is CIM app. Another one is TA for *nix where are modified those inputs values on setup screen. ... View more