mirror of
				https://github.com/Unleash/unleash.git
				synced 2025-10-27 11:02:16 +01:00 
			
		
		
		
	## About the changes Adds troubleshooting guides for some common problems under the how-to area (following the [diataxis framework](https://diataxis.fr/)). This is part of Unleash 2023 offsite challenge --------- Co-authored-by: Drew Gorton <drew.gorton@getunleash.io> Co-authored-by: Diego Susa <diego@getunleash.io> Co-authored-by: Michael Vittiglio <michael.vittiglio@getunleash.io> Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
		
			
				
	
	
		
			8 lines
		
	
	
		
			667 B
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			8 lines
		
	
	
		
			667 B
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| ---
 | |
| title: My feature flag is enabled but all/some of our users are not exposed to it
 | |
| ---
 | |
| 
 | |
| To confirm how users will have flags resolved, follow these steps:
 | |
| 1. The [Unleash Playground](../reference/playground.mdx) was developed with this particular use case in mind. An access token can be used along with context values (passed in via the UI) to see how a flag will be resolved. 
 | |
| 2. When using a **gradual rollout** strategy, be mindful of the **[stickiness](../reference/stickiness)** value. When evaluating a flag, if the provided context does not include the field used in the stickiness configuration, the gradual rollout strategy will be evaluated to `false`.
 |