Common Support issues and solutions on JOYN (Enterprise & OG)

	Module	Enterprise/ JOYN OG	Client	Issue	Reference Jira ticket	Possible solution/ Remarks	Module POC
1	Joyn Analytics	Enterprise	Pioneer	All Subscriptions not running for Pioneer today	WESS-16282	Triggering Manual subscription run to check the subscription feature. Checking and Removing unwanted DL’s from the root email account pool to enable pause on AWS root account	@a user / @a user
2	Joyn Analytics	JOYN OG	PetroSantander	Data in "Planta de gas" at "Reporte Diario de Produccion -LM PS" is at zero	WESS-15250	Possible data sync issue due to delay in Sync between FDG and Analytics.	@a user / @a user
3	Joyn Analytics	JOYN OG	PetroSantander	All data loaded are in zero in all official reports	WESS-16192	Require a View refresh from backend	@a user / @a user
4	Joyn Analytics	JOYN OG	PetroSantander	Missing data in Analytics module	WESS-16242	Require a View refresh from backend. Materialized calculated measure group refresh	@a user / @a user
5	Joyn FDG	JOYN OG	PetroSantander	LS-82 "downtime" does not appear	WESS-16333	This is know FDG issue where the downtime on FDG is miscalculating. currently we are running a script from backend to update the right Downtime o=in Dynamo.	@a user / @a user
6	Joyn FDG Allocations	JOYN OG	PetroSantander	Incorrect allocation of well LS-82	WESS-16400	This is know FDG issue where the downtime on FDG is miscalculating. currently we are running a script from backend to update the right Downtime o=in Dynamo. Additionally we ask client to run the allocation which resolves the issue.	@a user / @a user
7.	Joyn Analytics	JOYN OG	LLOX	Missing Data on Reports	WESS-13884	Possible data sync issue due to delay in Sync between FDG and Analytics.	@a user / @a user
8	Joyn FDG	JOYN OG	Exxon	Request to Delete records from table 132	WESS-16389	These records needs to be be removed from dynamo as the clients report these as soft delete issue which mean these records are deleted by the user from the UI and require permanent deletion from dynamo DB. Create a WEDEOPVS ticket to get the Team to run the script attached in the below sample tickets description. WEDEVOPS-31937	@a user / Devops teams