It is not generating when a new record is created. However, if the record was already created and you add the current record ID calculation, it will generate for the old record but not for the new one. Here is a video:
I can confirm it with a similar situation. It actually looks like the ID is already calculated correctly, but not displayed in the frontend. I have a ticket system, that checks inbound Mails, creates a ticket with number based on Unique ID.
While the frontend still shows NULL, the automated response in the mail already contains the correct result.
Indeed, there was an issue if calculation fields would not contain references to other fields, but only the record ID token - as in your scenario - they would sometimes not get calculated properly on record creation.
We pushed a fix today, could you verify on your end that this is now behaving as expected?
@Tim not working in my scenario - still broken… but I use the “unique ID” and its not using it in calculations for a new record. when I force the calculation with a little change again, it works.
Update: OK, its a different story to this one. And it was related, as I had two "unique field"s in my record. That should not cause this problem, but I solved it by only having one for now.