When users report a story log discrepancy, the first line of support will be the customer, i.e. the support contact assigned by the account holder. The support team should:
Check story logs in Analytics and check for any mismatch in log & meta when viewing log.
If the meta and log match, it's likely that the user has not completed the entire story. The user must then be directed to complete the story.
When a debug report is filed, the reseller account will receive the report. Using this report, the reseller support team can then compare what is on the device to what has been recorded on analytics:
Check the debug report against the logs in analytics.
If there the debug logs don't match up with the analytic logs, then the "Force Status" option can be used to match the device logs.
If the device logs match the analytic logs, the user must then be directed to complete the story.
If the device logs look incorrect or neither of the steps assists with the issue, then go to step 5.
Go through the story to see if you can replicate the issue. If an issue occurs, submit a debug report from the app and escalate to GitHub with the link, else proceed to step 6.
Ask the user to redo the story. If issues still occur ask them to resubmit a debug report and escalate to GitHub with a report link.
Top-level support for story logs is reserved for when all previous steps can not solve the issue. The following steps will be carried out from this level:
Review the debug reports
Check backend logs to check for issues
Replicate the issue based on provided information (Customer Support)
Respond with further steps to either gather more technical information, or by providing resolutions.
The app debug report allows the user to briefly describe their issue.
The user must submit the debug report from the device where the issue occurred.
Error logs are captured in the debug report which is used for technical stack tracing.
Debug reports show library items and story logs which assist in fixing analytic logs.