Date not populating correctly in Discipleship Journal

EDIT: Welcome to the user forums! /EDIT

Let me try to clarify: the date of the reading in the NASB bible doesn't show the (current) date you expect based on a Reading Plan that reflects readings in the discipleship journal, right?

In your screenshot it seems ("1 of 4") that there are several reading plans that have open readings for the same section of scripture. I'd suggest marking them as complete (or deleting them) in the Docs menu or at least turning them off in the Visual Filters menu, so you can see your current plan for 2021.

I only have one reading going right now.  It says 1 of 4 because that particular discipleship journal has 4 readings each day (Gospel, Epistle, Wisdom, OT).  My calendar has no readings at all listed for October.

I only have one reading going right now. (...) My calendar has no readings at all listed for October.

Maybe it's an artefact from the build of the RP? it says it started Sept 2019, maybe it has readings dated "October" which have been incompletely converted to Jan 2021 ("tomorrow"). Could you share the plan publicly? 

I think this is the link to the public share: https://fl.vu/q32dj

Thanks for your help.

I cannot get the dates to match correctly in the discipleship journal.  The date on the calendar does not match the date that populates in the Bible reading.

Thank you for your link. I believe I understand the problem...

The reading plan is designed for certain readings on certain days of the year... but you aren't reading those readings on those days. The only way to get them to match up is to synchronize YOUR reading with the plan. That is to say, read the "January 8th" reading on January 8. 

The reading of Jn 1:35 is actually on Oct 4 as per https://www.navigators.org/wp-content/uploads/2017/04/Discipleship-Journal-Bible-Reading-Plan-9781617479083.pdf . The RP shared by Robert also has large multi-day gaps, so it's broken.

The RP shared by Robert also has large multi-day gaps, so it's broken.

No. That is how the reading plan is designed. I have used it before. 

The reading of Jn 1:35 is actually on Oct 4 as per

yes, which is what I said before. There are certain readings for certain days. There is an "October 4th" reading, not a "day 276" reading. It is ok that Robert isn't reading the "October 4th" reading on October 4th, but the heading of "October 4th" won't change.

Robert - If you goal is to get them to line up, you will need to change the starting date of the plan to "January 1st" and keep up with the readings. Again, note that there ARE planned "make up days" (which is what Mick called "large multi-day gaps." 

The RP shared by Robert also has large multi-day gaps, so it's broken.

No. That is how the reading plan is designed. I have used it before. 

Ah, now I get that. It always reads 25 days per month. I saw a three-day-gap here and a six-day-gap there, but didn't figure it out and didn't read the PDF thoroughly enough.

EDIT: However, the plan still is broken. If edited to start on Jan 1 it will be correct until early April, after that the gap days and the calendar don't match up anymore.

Thanks for your help.  I appreciate the insight.  I deleted that plan to work through another.  My OCD would be challenged having to see two different dates each day! 

However, the plan still is broken. If edited to start on Jan 1 it will be correct until early April, after that the gap days and the calendar don't match up anymore.

Does the possibility of leap year account for that discrepancy? 

However, the plan still is broken. If edited to start on Jan 1 it will be correct until early April, after that the gap days and the calendar don't match up anymore.

Does the possibility of leap year account for that discrepancy? 

I don't think so. 

I noticed this date discrepancy as well, in early January. I chatted with Logos on it, and they recognized it is broken. They said they would submit the issue, and were unable to give an approximate date of resolution: could be ‘a couple days’ or ‘months’ or longer. Seeing it is still broken, I just submitted another ticket.