Generally associated with some connection problem, it can appear during various platform actions. Example: pulling a service in the Workspace, sending a document in the Workspace to the client, or even opening a report.
If it appears, perform a diagnostic and send a screenshot to our Support, explaining the context.
Failed to start in-person service
Usually happens when the attendant does not close a service from the previous day and gets stuck, unable to call another service.
A simple solution is for the attendant to enter the booth where the service got stuck and complete it, freeing the next ones.
Bounce Error when Sending Ticket
The error bounce (indicated by a red exclamation red next to the message in the inbox of the ticket) indicates that something unexpected occurred during sending, related to the recipient.
Examples:
a) Temporary rejections from the recipient's server.
b) Recipient's mailbox full.
c) Unknown recipient or non-existent domain.
d) Email delivered to the recipient's spam.
e) Recipient address on suppression lists.
In other words: if it identified the bounce in the error (soft_bounce / hard_bounce / recipient_bounce) you already know: the problem is not on the platform, but with the recipient.
Service Unit Blocked
If you try to generate an in-person service and this warning appears in yellow that means your service unit has been blocked here in Blocking of Opening Services.
In that case, contact your manager to perform the unblock.
No Outbound - Ticket configuration
This critical message in yellow appears when there are no incoming and outgoing configured.
Check if the three pages are correctly configured with incoming and outgoing emails.
1 - Incoming email configuration
2 - Outgoing email configuration
3 - General settings
You are probably missing configuring the incoming or outgoing email on one of the three pages mentioned above. After the adjustment, functionality will be normalized.
