Debug & Report Issues
How to report issues with the Package
Report issues or make feature requests in GitHub:
https://github.com/tsanetgit/SFDC_App/issues
Debug Salesforce issues
View errors in developer console
Navigate under Setting to the Developer Console

To view TSANet Errors open the resource and select the TSANetError__c.oj

The following command will show TSANet Connect Errors. You can add other fields as needed
SELECT Id, CreatedDate,tsanetconnect__Context__c, tsanetconnect__StackTrace__c, tsanetconnect__ErrorMessage__c, tsanetconnect__TSANetCase__c, tsanetconnect__Type__c FROM tsanetconnect__TSANetError__c ORDER BY CreatedDate DESC
Review the following fields on each returned record:
Error Message – high-level description of the error.
Stack Trace – technical details useful for developers.
Context – indicates the process that generated the error.
Type – categorizes the error.
Debug Authentication issues
To verify that authentication is working between the Salesforce App and the TSANet Connect backend open the New Collaboration screen and search for a member.

If results are returned the Authentication is working. If you receive an error check the following:
Verify the TSANet Credentials setting. Check that you have selected the correct environment and have the correct user/pass.
Only one TSANet Credentials record should be marked as Primary — having more than one can cause authentication to fail unpredictably.
Login to the WebApp with the user/pass to verify that the credentials you have entered are correct. If login fails there, reset the password and update the TSANet Credentials record in Salesforce to match.
Authentication can succeed while sync still fails. Check Setup → Scheduled Jobs and confirm the TSANet scheduled jobs exist and are running — a missing job can indicate a configuration or integration-user issue.
Debug Webhook issues
Select the Webhook Callback URL and verify that is returns the following
{"timestamp":"2026-07-03T13:26:50.944Z","status":"ok"}
If an error page is displayed then the setup in Salesforce is not correct. Review the configuration:
Connected App configuration
Site Guest User permissions (if applicable)
Remote Site Settings
Named Credentials
Webhook URL configuration in TSANet If Status is ok then check developer console for any errors (example permission issues), as well as debug logs for Apex exceptions, Flow failures, or record access issues. If status = ok and no errors, contact TSANet to validate webhook registration, endpoint configuration, and delivery logs.
Debug Permission issues
TSANet permission sets are included in the package and can be applied to both standard users and integration user. Profiles also need to have access to the Salesforce Case record. Available permission sets:
TSANet Connect Permissions (Admin)
TSANet Connect Permissions (Employee)
The affected user should have:
Access to the Salesforce Case object
Read/write access to TSANet custom objects
Access to the Flows used by TSANet Connect
Access to the Apex classes included in the package
The dedicated integration user (used for automated processes) should:
Have the TSANet integration permission set assigned
Be active, with API access enabled
Own or run scheduled TSANet jobs where required Integration-user permission issues have previously caused webhook and scheduled-job failures — check this user first if automated syncs stop working.
Última atualização