Wordpress sourcenodes error when switching post between draft/published. Live rebuild only.

[amcc]

On switching a wordpress post between published and draft I get an error in develop mode. This is a live-update error, but restarting develop does fix this.

Is it possibly because the published and draft appear as duplicate IDs, i do have a warning on this too.

I am using the current versions:
"gatsby-source-wordpress": "^5.1.0",
"gatsby": "^3.1.2",

I can test this by switching the default install wordpress "Hello world" post between published and draft.

I think this may be a bug - but thought i'd post here before submitting one to github.

output below:

warn  gatsby-source-wordpress  Found a duplicate ID in WordPress - this means you will have fewer nodes in Gatsby than in WordPress. This will need to
 be resolved in WP by identifying and fixing the underlying bug with your WP plugins or custom code.

 ERROR 

TypeError: Cannot read property 'databaseId' of undefined
    at forEach
(/Users/me/Sites/gmd/gmdgatsbywp/node_modules/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js:113:82)
    at Array.forEach (<anonymous>)
    at paginatedWpNodeFetch
(/Users/me/Sites/gmd/gmdgatsbywp/node_modules/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js:95:11)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at getWpActions
(/Users/me/Sites/gmd/gmdgatsbywp/node_modules/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/index.js:27:32)
    at fetchAndRunWpActions
(/Users/me/Sites/gmd/gmdgatsbywp/node_modules/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/index.js:84:21)
    at fetchAndApplyNodeUpdates
(/Users/me/Sites/gmd/gmdgatsbywp/node_modules/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/fetch-node-updates.js:44:36)
    at sourceNodes (/Users/me/Sites/gmd/gmdgatsbywp/node_modules/gatsby-source-wordpress/src/steps/source-nodes/index.ts:61:5)
    at runSteps (/Users/me/Sites/gmd/gmdgatsbywp/node_modules/gatsby-source-wordpress/src/utils/run-steps.ts:41:9)
    at runAPI (/Users/me/Sites/gmd/gmdgatsbywp/node_modules/gatsby/src/utils/api-runner-node.js:483:16)


 ERROR #gatsby-source-wordpress_112003 

 gatsby-source-wordpress 

        Encountered a critical error when running the sourceNodes.sourceNodes build step.
        See above for more information.

not finished source and transform nodes - 0.680s
not finished  gatsby-source-wordpress  fetch root fields - 0.646s
not finished  gatsby-source-wordpress  pull updates since last build - 0.646s

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] develop: `gatsby develop`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] develop script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/me/.npm/_logs/2021-04-16T11_42_50_172Z-debug.log
The terminal process "/bin/zsh '-c', 'npm run develop'" terminated with exit code: 1.