All Apps and Add-ons

Splunk Add On Builder Built Add On Configuration UI Page

addOnGuy
Loves-to-Learn Lots

The "configuration" page that the Add On Builder has created for my add on isn't matching the additional parameters that I've added for my alert action. Instead, the configuration page seems to somehow show the parameters I used for a prior version. I've checked the global config json file and everywhere else I could think of and they all reflect the parameters for the new version. Despite that, the UI still shows the old parameters. Does anyone have any idea why or where else I could check?

Labels (2)
0 Karma

livehybrid
SplunkTrust
SplunkTrust

Hi @addOnGuy 

Try hitting the bump endpoint to clear the internal web cache.

https://yourSplunkInstance/en-US/_bump

Then click the "Bump Version" button:

livehybrid_0-1753942520427.png

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

 

0 Karma

PrewinThomas
Motivator

@addOnGuy 

-Try clearing your browser cache or using an incognito window
-Check both default and local directories inside your add-on - Old parameters might be lingering in local.
-Restart Splunk

If all else fails, try exporting the current version and re-importing it into Add-on Builder as a fresh projectand try.


Regards,
Prewin
Splunk Enthusiast | Always happy to help! If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...