This isn't technically a form/workflow but I have found that certain event viewer errors are red flags for issues with workflow and forms and have created a task scheduler event that triggers on when these events come up and run a PowerShell script to send our team an email with event details and common things to look for when troubleshooting.  Also handy for getting notifications that LFDS has more users trying to sync in from AD than we have licenses for them.  

I will post more detail if other people are interested but the code to send the email I just asked AI and the task scheduler process is easily created by right clicking on the event and choosing to create a task scheduler event. 

Last bit of advice build in a delay to keep the script running for 5 minutes after the first trigger.  That way you don't get buried with repetitive emails.  Task scheduler default is not to trigger again as long as the script is running.

Whenever I need to guess how much time a workflow is going to run (based off of the number of documents it has to process), I use a "Search Repository" task to query the parent folder with {LF:Name="*", Type="DS"} & {LF:LOOKIN="(parent folder)".  Then I click on the "Test Search Query" to get a count of the number of documents.  I can then narrow the parent folder to reduce the number of documents.

I realized I had a bunch of reports I was running monthly, and re-built them all as workflows that generate emails.  The results all come from various database queries and searches, from 4 different databases, but I can access them all from Workflow.  I have the workflow cycle through each result, it determines if the iteration of the loop is even or odd and creates a line of HTML code that includes colors (that's why the even and odd are different, since there are different colors for the two) - basically I'm building the row of a HTML table for each result, and adding that to a multi-value token.  Then at the end, it creates an email that starts and ends the HTML table, putting the token with the rows into the body of the table.  The end result is that I get my query results as a pretty HTML table in an email, automatically on whatever schedule I need it.

Note - you should probably edit this and change it from the question post to a discussion post.