if there’s a start to close timeout, and the task takes longer than this timeout, I can see an Activity Task Timed Out event is logged.
What I don’t understand is why the workflow continues? it seems like no error is thrown in a try catch (typescript).
If you see ActivityTaskStarted and ActivityTaskTimedOut event in history, means that
last attempt of your activity timed out (the ActivityTaskTimedOut event would give you specific which activity timeout lead to this for the last attempt).
On activity failure (so after all retries defined), server does deliver Activity error to your workflow code. Your code can handle this error and continue execution based on business logic, thats my guess whats happening for your second question.