Limits worth knowing before you commit
None of this is hidden in an issue tracker. If one of these lines is a dealbreaker, finding out now costs far less than migrating off later.
Your function runs from the top over and over and nothing in the syntax says so. A casual time.Now() or one stray database read sends two runs down different branches, and nothing catches it for you.
Every round runs the whole function again. A few dozen steps is comfortable. Thousands will hurt, and the cost grows with the length of the flow, not just its width.
A flow runs for three days, you deploy a version that adds a step, and the in-flight instances run straight into the new code. Temporal solves this with a patch API. gotick doesn't, yet.
The flow-level WithTimeout option exists in the API and is accepted, but nothing reads it yet — a flow will not time out on its own. Use WaitForSignal with a timeout, or an explicit Sleep, when you need a deadline.
There are no cross-language SDKs, and it hasn't been proven at anything like Temporal's scale. If a flow going wrong costs real money, weigh that before committing.
Something missing here?
If you read this far, wanted to use gotick, and stopped one step short — that step is the most useful thing you could tell us. It beats any roadmap.
Open an issue