complete TF position required - error with basic projections.

Hi All,

I seem to be seeing a LOT of these errors when doing basic projections.


System.ArgumentException: complete TF position required

Parameter name: committedEvent

at EventStore.Projections.Core.Services.Processing.EventByTypeIndexPositionTagger.IsMessageAfterCheckpointTag(CheckpointTag previous, CommittedEventDistributed committedEvent) in c:\work\EventStore\src\EventStore.Projections.Core\Services\Processing\EventByTypeIndexPositionTagger.cs:line 34

at EventStore.Projections.Core.Services.Processing.ReaderSubscriptionBase.ProcessOne(CommittedEventDistributed message) in c:\work\EventStore\src\EventStore.Projections.Core\Services\Processing\ReaderSubscriptionBase.cs:line 95

at EventStore.Projections.Core.Services.Processing.HeadingEventReader.DistributeMessage(CommittedEventDistributed message) in c:\work\EventStore\src\EventStore.Projections.Core\Services\Processing\HeadingEventReader.cs:line 205

at EventStore.Projections.Core.Services.Processing.HeadingEventReader.Handle(CommittedEventDistributed message) in c:\work\EventStore\src\EventStore.Projections.Core\Services\Processing\HeadingEventReader.cs:line 97

at EventStore.Projections.Core.Services.Processing.EventReaderCoreService.Handle(CommittedEventDistributed message) in c:\work\EventStore\src\EventStore.Projections.Core\Services\Processing\EventReaderCoreService.cs:line 156

at EventStore.Core.Bus.MessageHandler`1.TryHandle(Message message) in c:\work\EventStore\src\EventStore.Core\Bus\MessageHandler.cs:line 33

at EventStore.Core.Bus.InMemoryBus.Publish(Message message) in c:\work\EventStore\src\EventStore.Core\Bus\InMemoryBus.cs:line 324

at EventStore.Core.Bus.QueuedHandlerMRES.ReadFromQueue(Object o) in c:\work\EventStore\src\EventStore.Core\Bus\QueuedHandlerMRES.cs:line 121














function(state, event) {

if (! return null;

if (! return null;

linkTo(“recipient-” +, event);

if (! return null;

linkTo(“sender-” +, event);

if (! return null;

linkTo(“subaccount-” +, event);


Any ideas?


The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax Media does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax Media does not accept legal responsibility for the contents of this message or attached files.


This is a known issue, it’s tracked here (actually your exact case):

It’s nothing to worry about necessarily in the short term - it will likely be resolved in the next release along with several other projections issues. Note that projections are still a beta feature though and have no guarantees whatsoever around them.



Hi James,

Thanks for getting back to me.

Is there an ETA on when projections are going to be considered stable? Are there any customers using projections in production deployments?

I’m about to put upwards of 50 million events per month into this thing…