Available in: Axsy Mobile for Salesforce, Axsy Field Service, Axsy Public Sector, Axsy Retail Execution
If you see a INVALID_SESSION_ID or a 401 error as shown in the two examples below after you have attempted to publish a new sync config which halts in Draft status, the likely resolution to this issue if found below.
ResolutionCheck Setup -> Session Settings and uncheck Lock sessions to the IP address from which they originated
Making this change should enable you to publish your sync config successfully.
When the meta data associated with a sync config is published the Axsy web app makes API calls using a different IP address to the one you login as a user. Therefore unlocking this session setting will remove the lock that prevents a new sync config from being published.