Skip to main content

We’re excited to announce the Automation Logs!

Since our last update, we’ve gathered feedback, made several enhancements, and now we’re officially launching.

⭐️What’s new:

  • Enhanced Access: You can now access logs directly from the pipe’s automation list.
         -  This new entry point allows users to search by card name, card ID, or automation name.
         -  Users can also filter by status, a feature previously available within each individual rule.
     
  • Transparency Boost: We’ve clarified that the logs display data from the last 3 months to ensure transparency for pipe admins.
     
  • Feedback Channel: We’ve implemented a direct channel for users to report any issues with the logs.
     
  • Improved Error Messaging: More errors now display contextual messages, helping users better understand what might be amiss in their setups. While not all errors are yet captured, the most common issues, like unconnected pipes or unfilled required fields, are covered.
     

     

🎓 Click here to access the help article to find out more about this new feature.



Your feedback is invaluable, feel free to leave your comments in this post.

Great functionality!! Thank you so much!

It’s missing the error message or some information about the reason that automation was failed.

👏👏👏👏👏👏

Hi Pipefy team, could you add an option to export the automation logs (with criterias like: Start Date / Finish Date), Status to .csv, .xlsx, .pdf? It’ll be very helpful. Thanks

@Ezequiel Souza If you click on the expand button on the log, you will be able to see details about that log, including the error message. There is a mechanism directly on them to send feedbacks if a specific error is not clear or not helpful for your scenario, just send us a thumbs up and/or down there.

Regarding your second point, whats the purpose of exporting those logs? What will you do, or achieve, with the export report? So we can see if can improve to achieve that inside the product.

Hi Rodrigo.

I can’t see any details about the failure:

 

One of the purposes is create a view to identify the volume of automation failures to identity the offensors and fix them. 

 

 

Ótima sugestão!

Got it @Ezequiel Souza , as mentioned in the post, not all errors are yet captured, but the most common issues are, such as these:


We will keep updating more and more errors each week. For the errors not yet mapped, please contact support and they will investigate and send us new errors to implement on logs.

Regarding the identification of failures, it makes sense, in future versions we plan to have more support on that, to make it even more visible to pipe admins, so you don't need to run any extra analysis. Keep tuned here on the community for updates.

Thanks!

This feature is really amazing!
Thank you.

Terms & ConditionsCookie settings