Typically with a SAFEQ Cloud implementation, any areas to troubleshoot surround the SAFEQ Cloud API integration.
After inserting the API details for the first time, the Intuitive integration may need to be authorized in the SAFEQ Cloud interface.
To check this, first make a note of the Client ID in the Intuitive for SAFEQ Cloud connection. Next, login in to SAFEQ Cloud, open the Integrations, find the Client ID you noted earlier and check that there is a green tick next to the Endpoint ID matching your client ID.
If the ID is green, you can move on to the next step. Otherwise, if it is red, you will need to authorize the integration manually.
To do so, edit the endpoint by selecting the checkbox next to its ID, then select “Authorize Selected”
After authorizing the connection, you will need to force a refresh of the API connection. To do so, open ETL Management and refresh the connection “SAFEQ”.
If the authorization is green, we can check the log files to see if there’s any additional information. Opening the connection again, open the Activity Log.
Whilst the contents of the log file may be unique to you, you may be able to infer some additional details from this stage.
Otherwise, we can also check the datafeed logs to see what messages are there too. Opening one of our feeds, we can open the Activity Log to see when the last successful import occurred on. If you are noticing that the feeds are refreshing correctly, one alternative is that there has been no data produced in SAFEQ Cloud since the last successful import.
To check this, login to SAFEQ Cloud and locate print-related jobs that have occurred since the last successful import. If there have been no jobs, then there may have been no new API data to import since then. One area to confirm this, is to check the last available date in the User Profile dashboard. You can check the user activity drilldowns and grab the latest date from this screen.
Otherwise, you may need to raise a ticket with Intuitive support to investigate. However, before doing so, we need to collate the information we obtained earlier, including, but not limited to:
- Screenshot of the Authorization status of the Client ID (Endpoint ID)
- Confirmation that SAFEQ Cloud is currently licensed
- Confirmation that SAFEQ Cloud is on version 3.40 or newer
- The contents of the “SAFEQ” Connection Activity Log
- Copy to clipboard, export to TXT file
- The contents of the Datafeed “Document History” Activity Log
- Copy to clipboard, export to TXT file
- A screenshot of the last available timestamp from the User Profile dashboard