Falkor has selected data that is available for export. To learn more about this feature please see Exporting.
For issues that require deeper investigation, users may be asked to Send a Debug Report to Falkor.
If a user's logs are persistently failing to upload, you can ask them to send a debug report from their account. This will send Falkor a report to investigate device log issues.
To send a Debug Report, the user will need to:
Open the app and go to "Account"
Under "Information", select "Send Debug Report"
Choose "Yes" to send
If you are a Falkor backend user and are unable to see analytics on your Analytics page, please check the following:
That you have the correct user permission (your Falkor Agent can check this).
Try using the platform by opening a browser tab in incognito mode. If the analytics load, then it's likely that you have a plugin (e.g. anti-virus or ad-blocker plugin) that is blocking required scripts to run Falkor.
To permanently resolve a plugin from blocking Falkor displays, you can whitelist the falkor.io domain in any anti-virus or ad-blocking plugins.
Open a story in Authoring & select Story from the top menu. Select Builds & Archives from the dropdown to see all the builds and date when each build was released.
When a user reports that they have completed a story, but their logs do not reflect the same status on the backend, you can manually edit the logs.
You can edit the score (if max. score was set), duration, and status of the log.
In Analytics, open a story, and then got to Logs. From here you can select the cogwheel icon for any specific user and then select "Force Status". Force Status allows you to manually enter the time taken to complete a story, and to set the status (In Progress or Completed).
Exports from Falkor use a semi-colon delimiter with quotes as a string delimiter. When opening a CSV export, please open it with these options. Generally, most Excel programs have this set as the default.
If column headings are missing or fields are missing, it is possible that these options were not applied.
In some cases, a user claims to have completed a story yet the completion logs are not available in analytics. Although this can be investigated on a server-level, we often find that there are two reasons for missing logs:
The user did not complete any stories (or there is confusion / a misunderstanding around this).
The user's data was removed from analytic logs by a backend account administrator.