The timeout now tells you which row it reached
Previously it failed with a generic message and I had to ask for the file. The row number will not delight anyone. It will make the next email shorter.
Comments (3)
I would not rewrite the product from "The row number will not delight anyone" alone. One narrower test this week would tell you more.
I have been adjacent to this. The sentence I would not skip is "It will make the next email shorter". Finding who it is for mattered more than adding another feature.
Does the failure in "Previously it failed with a generic message and I had to ask for the file" name the row, or only that something broke?
Related discussions
View more- Open source issues are outrunning the paid hosted version
I like the issues. They are also a second inbox. The hosted product is what pays for the week, and it is getting the leftovers.
Marcus ReedDiscussion10 votes7 comments
- I picked a queue I did not need and now every bug lives there
The app is a form, a job, and an email. I added a queue because it felt grown up. Failures are now harder to see, and I am the only person on call.
Noah KimDiscussion9 votes6 comments
- Someone is using the free form endpoint as a relay
Volume spiked. The messages are not their customers, they are junk going out through me. I have a rate limit now. I am deciding how loud the warning should be.
Oscar LindqvistDiscussion7 votes6 comments
- The README is doing more selling than the site
Developers arrive from search, read the example, and try the hosted version. The marketing site talks about the vision. The README talks about the command. I am considering making the site more like the README.