Validate your test configuration

Use Try Now to validate the configuration of a synthetic test.

In Splunk Synthetics, test runs are either ephemeral or persisted:

  • Ephemeral runs are those whose results are not stored or used for monitoring; their results don't affect run metrics. Try Now runs are ephemeral.

  • Persisted runs are those whose results are stored and used for monitoring. All synthetics tests that you schedule are persisted. In addition, Run Now runs are persisted.

Here is some guidance on when to use each type of run.

Type of run

Use cases

Try Now

  • Check that the steps you added to a new or existing test are correct.

  • Validate your test configuration.

Scheduled

  • Review run results.

  • Run a test on a schedule.

Run Now
  • Run a test on demand.
  • Verify that a fix you made (either to the test or to the application) resolves a failed test run.
How to use Try Now

As you add steps, select Try Now to see if the steps are valid.

Use case scenarios

If you have a browser test which monitors an add to cart workflow, you can add a set of steps to verify that users can add a promo code during the payment process.

  1. Open the edit view of the test.

  2. Add a set of steps for the promo code process.

  3. Select Try Now to run.

The results from the try now run show whether or not the test completed successfully. If there is an issue with one of your steps, the try now results show which step is the problem and you can troubleshoot before adding the test to your monitoring suite.

Limitations

  • You can run a maximum of 1,000 Try Now runs per hour for each organization.

  • Try Now runs have a strict timeout limit of 5 minutes. This includes the time spent waiting in the test queue, executing the test, and processing and saving the results. If the full workflow exceeds 5 minutes, the run fails with the message Test validation request timed out even if the test would normally succeed under standard conditions.