We fixed an issue where some files uploaded to an application would display a 403 error when trying to access them through the Application view. This issue is resolved and files are now visible on applications as expected.

We fixed an issue that caused a 500 error to be shown when accessing a broken Salesforce connection. In some cases, a Salesforce connection could enter an invalid state where it was not authenticated but the application did not identify it as disconnected, causing an error to occur. We resolved this issue and connections will be marked as disconnected properly when authentication has failed, allowing the connection to be re-authenticated.

We fixed an issue where the “Send From” field on an email action in an automation would revert back to the site’s custom sender email address when selecting the noreply@mail.smapply.net address. Previously when an automation with this action was saved, if the site had a custom sender address selected as the default sender, the email action would default back to that custom sender even after having been changed back to Apply’s default email address. This has been resolved and email actions can now be saved with a custom sender or the default sender as needed.

We added a warning message on automation actions related to unassigning reviewers which indicates that the data will be permanently deleted. Now when accessing or creating a new automation, if an unassignment action is included in the automation, a warning message will be shown.