Notice types

A notice is raised by the integration, sender or export it concerns, carries a Type (Temporary for a passing failure, Permanent for one that needs a change) and a Level (Warning or Error), and is addressed to particular people. The same cause repeating updates the existing notice’s Last triggered at rather than adding a row.

Delivery and sender notices

Title	Raised by	Cause	Who sees it	Resolves with
Delivery bounced	Slack, SendGrid email, Google Workspace, Microsoft 365, Teams	A delivery could not be sent: an inactive integration, a sender in error, a temporary or permanent error from the channel, a misconfigured sender, or raw HTML email not being enabled. The message lists Recipient, Message, Flow and Reason.	The workspace owner; every admin as well, with an email, when Send email when a delivery bounces is on.	Resend on the notice, or Resend on each delivery in Activity.
Ticket bounced	Jira	A ticket step could not create its ticket.	The workspace owner.	Fix the Jira connection, then resend.
Re-authentication required	Slack, Google Workspace, Microsoft 365, Teams, Jira	The integration’s or a sender’s credentials stopped working (The credentials for the Slack sender are not valid, and so on).	Admins and owners, with an email, when Email admins and owners when re-authentication is required is on; otherwise the owner.	Reconnect the sender or integration in Settings; it is listed under Needs Attention there.
Slack connection error, Google Workspace connection error, Jira connection error, SendGrid connection error	The named integration	Pyn’s connection to the service failed.	The workspace owner.	Usually clears on its own; reconnect if it repeats.
Mailbox unavailable	Microsoft 365	The sender’s mailbox could not be reached.	The workspace owner.	Check the mailbox in Microsoft 365.

HRIS and ATS notices

Title	Cause	Who sees it	Resolves with
HiBob Reauthentication Required, BambooHR Reauthentication Required, Workday Reauthentication Required, Rippling Reauthentication Required, ADP Reauthentication Required, Greenhouse Reauthentication Required, Ashby Reauthentication Required	The connector’s credentials were rejected during a sync.	The workspace owner.	Reconnect the integration in Settings.
HiBob Insufficient Permissions, BambooHR Insufficient Permissions, Rippling Insufficient Permissions, ADP Insufficient Permissions, Greenhouse Insufficient Permissions, Ashby Insufficient Permissions	The credentials work but lack access to a field or endpoint Pyn reads.	The workspace owner.	Grant the permission in the HRIS, then refresh.
BambooHR Reconnect Required, Rippling Reconnect Required, ADP Reconnect Required	The connection must be made again.	The workspace owner.	Reconnect in Settings.

The message on each carries the connector’s own error text; the integration’s History tab in Settings has the full log.

Webhook and export notices

Title	Cause	Who sees it	Resolves with
[Webhook name] rejected a payload	An inbound webhook received a request it could not accept: a bad secret, an unknown employee, a payload the form did not take. The message carries the reason.	The workspace owner; every admin, with an email, when Email admins when a webhook cannot take a payload is on.	Fix the caller; Archive the notice.
[File name] is ready to download	An export you started has finished.	You only.	Download within seven days.

States

A notice is open when raised. Archive or Close moves it to closed and into the Archived view; Resend on a bounce notice closes it as part of the action. A notice can also be marked acknowledged (seen but not resolved) by other parts of Pyn; it still shows under Open until closed.

Related

• Choose which notices are emailed for the three email settings named above.
• Resend bounced deliveries from a notice for the Resend action.
• Enrollment, step and delivery statuses for Bounced and Bounced* in Activity.