Skip to main content

Platform 19.4 Release 🏭

When will I receive Platform Release 19.4?

⬆️ We expect most of the rollout to be completed by mid‑February. There’s no need to refresh your Pia tenant, you’ll automatically receive an email with the Release Notes as soon as the latest version becomes available to you.

Bug Fixes πŸ›β€‹

  • Fixed an issue where the user sessions were incorrectly timed in Pia Canvas if the user forgot to clock out. (#27899)
  • Resolved a UI issue where the SmartForms settings icon in the SmartForms portal was invisible if the theme color was set to white. (#28528)
  • Fixed an issue where Pia was storing API Tokens for third party CSPs longer than its validity causing automations to fail during license provisioning. (#28823, #29734)
  • Fixed an issue where inactive contacts were appearing within the "Route to Assignee" action of the AI Triage Dispatch rules screen. (#28918)
  • Resolved an issue where Pia was disabled for clients of a Partner when migrating the clients from one ticketing system to another. (#29028)
  • Resolved an edge case for a Partner where they were unable to access Pia in their ConnectWise ticketing system with Nilear Interface. (#29082)
  • Resolved an edge case for a Partner where the AI Triage feature was including tickets that needed to be skipped. (#29293)
  • Fixed an issue in the Agents screen where the paging was not working properly. (#29385)
  • Fixed an issue for a Partner where clients were shown as un-configured in the adoption report. (#29453)
  • Made the Pia tenant more resilient to handle a specific scenario where Triage was causing a performance issue. (#29547)
  • Fixed an issue in AI Triage where the config watcher incorrectly reported a configuration error despite valid settings. (#29590)
  • Resolved an edge case for a Partner where the tickets created via the SmartForms requests were classified incorrectly. (#29618)
  • Fixed an issue where a scheduled AutoTask ticket for Pia: Staff Offboarding automation was failing due to Pia attempting to assign an inactive user to the ticket. (#29645)
  • Resolved an issue where the chatbot was not automatically re-enabled if a ticket upon re-opening a closed ticket. (#29661)
  • Fixed an issue where cancelling automations did not automatically cancel time logging for the Partner. (#29764)
  • Fixed an issue in AI Triage where a permission error prevented company data from being collected, causing the existing company ID to be overwritten and resulting in an error. (#29797)
  • Resolved an issue where the log entries for automations were displaying incorrect times due to missing time zone conversion in the Live Packages screen (#29801)
  • Resolved an issue where the SmartForms: Staff Onboarding automation was failing during Active Directory Sync due to unexpected connection issue against a machine. (#29882)
  • Resolved an issue where Partners were seeing Pia health alerts for invalid Triage mappings even when their configuration was correct. (#29911)
  • Fixed an edge case for a Partner where a scheduled automation was sending duplicate notification emails. (#29960)
  • Fixed an issue where the Pia: Triage V2 automation was failing when attempting to retrieve errored activity logs. (#30006)
  • Fixed an issue where the Pia: Triage V2 automation was failing when attempting to retrieve ticket data due to restrictions in Halo ticketing system API. (#30008)
  • Fixed an issue for a Partner where the Pia chatbot was not opening in AutoTask after the authentication update to the Pia Portal. (#30046)
  • Resolved an issue for a Partner that was causing extended Triage processing times. (#30066)
  • Fixed an issue where the Partner was unable to find a contact type when creating a new contact sync rule in the SmartForms screen. (#30137)
  • Resolved an issue where re-selecting an approver did not automatically update the approval email field while creating a new approver in the Approvers Tab of the clients screen. (#30145)
  • Resolved an edge case affecting a Partner where guest access authentication was failing for a user in Pia tenant. (#30212)
  • Fixed an issue where Pia was not working within the AutoTask ticketing system due to webhook data failing to ingest correctly. (#30222)
  • Resolved an issue where Pia encountered an admin‑consent error that required Partners to authorize MS Graph twice. (#30229)
  • Fixed an issue where a Partner experienced performance slowness on the Users screen. (#30243)
  • Fixed an issue where the Microsoft Graph API was not authorizing for a Partner due to exceptions in the assigned role. (#30277)
  • Fixed an edge case for a Partner where a misconfigured Get Approval activity caused an unintended additional approver to be emailed during an automation. (#30312)
Stay Connected with us at Pia! ⚑

Your feedback matters to us! πŸ’œ πŸ› οΈ We're here to address any issues or suggestions you have, just drop us a line at

partner-support@pia.ai for assistance.

#πŸ’‘Got ideas to enhance our platform? Share them at ideas.pia.ai and shape the future of Pia aiDesk!
βš™οΈ Ready to supercharge your automation journey?
Your Partner Success Manager is your go-to person. Reach out to them to explore custom automation possibilities and optimize your journey with Pia aiDesk.

Let's make AI and automation magic together! πŸš€