Skedulo X can sometimes run into problems trying to connect to its server. If this occurs, Skedulo X will display the error on screen.
As a Normal End User (Resource)
If you experience this type of error, i.e., a server error, it would be great if you could capture a screenshot (or write down the text that is displayed) and pass it onto your support team. These types of error cannot be fixed by simply closing the Skedulo X mobile app and starting again as the error is not coming from in the app itself.
Figure 1. Skedulo X displaying server errors which occurred due to the end user not having the correct permission set assigned in the CRM.
As an Admin for the Organization
Reading the returned error, it is possible to identify areas that might be preventing your resource from successfully logging into Skedulo. Using figure 1 (above) as an example, a Skedulo object could not be found, the error text suggests checking the configuration of the Skedulo package and permissions as possible causes of the problem. These items are configured in the CRM (in this example Salesforce), rather than in the Skedulo web app.
The following points could be useful to check:
- Does the end user have a Skedulo license applied?
- Is the User account unfrozen?
- Is the User account active?
- Does the User have either the Salesforce or Salesforce Platform license?
- Does the User account have the Resource Permission Set applied?
- Does the User account have a Custom or Cloned Permission Set applied? (If so, we strongly suggest you add the "Baseline Permission Set" as well—to provide the minimum recommended access to Skedulo objects).
- Does the User account have the "skeduloUserType" set to Resource?
Figure 2. Skedulo X displaying a Salesforce login failure due to the user account being frozen on the CRM.
Figure 3. Skedulo X displaying a server error which occurred when the user is set as inactive in the CRM.
Also, see Skedulo Permission Sets.