Hi,
I am facing the mentioned error while setting up Forecast Actions. I checked the data types in both the source and target module, they are the same. Still getting the error.
Please let me know what can be the reason for this error.
@mukulsharma , this typically means that import action that is used by PlanIQ is somehow misconfigured.I could only recommend that you contact support and they will be able to help you from there.
Thank you,
Hi,I saw this with another customer. It was caused by misconfiguration of timestamp in the import action in particular. It should be Y-M-D.
Hopefully this helps.
Thank you.
Thanks Evgyk,
Let me check with the Anaplan support on this.
@mukulsharma this is likely a result of PlanIQ recognizing historical values for one (or many) forecast nodes however these nodes are not present in the target. I.e., if you're feeding PlanIQ from DH, ensure your forecast node list is 1:1 with the target (spoke).
Could be a number of reasons for this errors message; however when I received it, this was the fix. Hope this helps.
Check out the latest Anaplan feature updates and enhancements in our January 2026 official release notes. The information below offers supplemental information to that post. Dataspaces in Anaplan Data Orchestrator Dataspaces are partitioned areas of a tenant-wide Anaplan Data Orchestrator instance. Integration…
If you missed our January 29, 2026 platform release event, the recording is now available! In this webinar, we highlighted the most recent feature releases and how to take advantage of these in your environment. Our expert-led session demonstrated new features and innovations, provided a technical deep-dive and “how-to”,…
