As described in another thread (Provide initial state to Apache Flink Application) - the situation was fixed using a separate init deployment which consumes the topic and writes the data to the Flink state.

Then a savepoint is created before starting the proper application from this savepoint with the data