🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:
Response:
Calculated Shard: 168 (from laksa098)

2. Crawled Status Check

Query:
Response:

3. Robots.txt Check

Query:
Response:

4. Spam/Ban Check

Query:
Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

đź“„
INDEXABLE
âś…
CRAWLED
7 months ago
🤖
ROBOTS ALLOWED

Page Info Filters

FilterStatusConditionDetails
HTTP statusPASSdownload_http_code = 200HTTP 200
Age cutoffPASSdownload_stamp > now() - 6 MONTH7.9 months ago (distributed domain, exempt)
History dropPASSisNull(history_drop_reason)No drop reason
Spam/banPASSfh_dont_index != 1 AND ml_spam_score = 0ml_spam_score=0
CanonicalPASSmeta_canonical IS NULL OR = '' OR = src_unparsedNot set

Page Details

PropertyValue
URLhttps://learn.microsoft.com/en-us/answers/questions/5110518/use-of-exponential-smoothing-formula
Last Crawled2025-08-25 11:20:40 (7 months ago)
First Indexednot set
HTTP Status Code200
Meta Titleuse of exponential smoothing formula - Microsoft Q&A
Meta DescriptionHi I am trying to get the FORECAST.ETS formula to work but its returning me a #NUM! error. My formula is =FORECAST.ETS($A1005,$B$2:$B$1004,$A$2:$A$1004,1,1,1) $A$1005 refers to the target date while $B$2:$B$1004 is the data values range and $A$2:$A$1004…
Meta Canonicalnull
Boilerpipe Text
Hi I am trying to get the FORECAST.ETS formula to work but its returning me a #NUM! error. My formula is =FORECAST.ETS($A1005,$B$2:$B$1004,$A$2:$A$1004,1,1,1) $A$1005 refers to the target date while $B$2:$B$1004 is the data values range and $A$2:$A$1004 is the time range. The linear method with formula =FORECAST.LINEAR($A1005,$B$2:$B$1004,$A$2:$A$1004) works perfectly so it would seem the arguments are correct. I'm wondering if the dd/mm/yyyy formatted time range could be the problem? Is that a supported time range?
Markdown
[Skip to main content](https://learn.microsoft.com/en-us/answers/questions/5110518/use-of-exponential-smoothing-formula#main) This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. [Download Microsoft Edge](https://go.microsoft.com/fwlink/p/?LinkID=2092881%20) [More info about Internet Explorer and Microsoft Edge](https://learn.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge) Add Add #### Share via [Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F5110518%2Fuse-of-exponential-smoothing-formula%0A%09%09%09%09%09%09%09%09%09%09%09) [x.com](https://twitter.com/intent/tweet?original_referer=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F5110518%2Fuse-of-exponential-smoothing-formula%0A%09%09%09%09%09%09%09%09%09%09%09&text=use%20of%20exponential%20smoothing%20formula%0A%09%09%09%09%09%09%09%09%09%09%09&tw_p=tweetbutton&url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F5110518%2Fuse-of-exponential-smoothing-formula) [LinkedIn](https://www.linkedin.com/cws/share?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F5110518%2Fuse-of-exponential-smoothing-formula) [Email](<mailto:?subject=&#10;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;%5BShared%20Question%5D%20use%20of%20exponential%20smoothing%20formula&body=use of exponential smoothing formulahttps%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F5110518%2Fuse-of-exponential-smoothing-formula>) # use of exponential smoothing formula ![](<data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E>) Anonymous 2021-02-07T08:20:39+00:00 Hi I am trying to get the FORECAST.ETS formula to work but its returning me a \#NUM! error. My formula is =FORECAST.ETS(\$A1005,\$B\$2:\$B\$1004,\$A\$2:\$A\$1004,1,1,1) \$A\$1005 refers to the target date while \$B\$2:\$B\$1004 is the data values range and \$A\$2:\$A\$1004 is the time range. The linear method with formula =FORECAST.LINEAR(\$A1005,\$B\$2:\$B\$1004,\$A\$2:\$A\$1004) works perfectly so it would seem the arguments are correct. I'm wondering if the dd/mm/yyyy formatted time range could be the problem? Is that a supported time range? Microsoft 365 and Office \| Excel \| For home \| Windows [Microsoft 365 and Office \| Excel \| For home \| Windows](https://learn.microsoft.com/en-us/answers/tags/1168/m365-office-office-excel-home-platform-windows/) ![](https://learn.microsoft.com/answers/media/logo-ms-social.png) Sign in to follow Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. 0 comments No comments Report a concern I have the same question I have the same question 0 {count} votes ## 4 answers Sort by: Most helpful [Most helpful](https://learn.microsoft.com/en-us/answers/questions/5110518/use-of-exponential-smoothing-formula?orderby=helpful&page=1#answers) [Newest](https://learn.microsoft.com/en-us/answers/questions/5110518/use-of-exponential-smoothing-formula?orderby=newest&page=1#answers) [Oldest](https://learn.microsoft.com/en-us/answers/questions/5110518/use-of-exponential-smoothing-formula?orderby=oldest&page=1#answers) 1. ![](https://techprofile.blob.core.windows.net/images/dQLghcQVf0iX-PuiJC7CFg.png?8DCAF1) [HansV](https://learn.microsoft.com/en-us/users/na/?userid=85e00275-15c4-487f-97f8-fba2242ec216) • 461\.6K Reputation points • MVP • Volunteer Moderator 2021-02-07T13:28:10+00:00 The formula itself is OK; it might be a peculiarity of your dates. According to the documentation for FORECAST.ETS: "The dates in the timeline must have a consistent step between them and can’t be zero. The timeline isn't required to be sorted, as FORECAST.ETS will sort it implicitly for calculations. If a constant step can't be identified in the provided timeline, Forecast.ETS will return the \#NUM! error." 0 comments No comments Report a concern 2. ![](<data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E>) Anonymous 2021-02-07T13:49:28+00:00 Thanks Hans. I did see that earlier although I didn't understand what "constant step can't be identified" means - like how do we even know it exists and solve for it. Anyway I solved it by replacing the dates with a numerical sequence with step of 1 from 1 to N and that seemed to have done the trick\! I think it should work with dates but for some reason didn't at least in my case. Not sure if there's a bug but I hope Microsoft takes note of this on future releases. 0 comments No comments Report a concern 3. Deleted This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our [Code of Conduct](https://aka.ms/msftqacodeconduct) for more information. *** Comments have been turned off. [Learn more](https://aka.ms/msftqadelete) 4. ![](<data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E>) Anonymous 2021-02-07T21:40:21+00:00 Fortunately in my case the dates are indeed daily so I think the fix I made is correct. I also read somewhere that FORECASTING.ETS can also work with numeric sequences that correspond to time periods but the intervals need to be the same, not necessarily a day for each date. They could be weeks, months or days as long as the time intervals are consistent. I'm more concerned about why it failed to work for dates when it should have. I'm not sure if the failure was due to dates that were not spaced exactly a day apart at the dates corresponded to stock trading days which would essentially be business days but the formula should have adjusted for that. But the data points would have been consecutive as each stock trading day even if they end on a weekday and therefore skip weekend dates would have been consecutive business days and thus converting to a numeric sequence of 1 apart might be the workaround. 0 comments No comments Report a concern *** ## Additional resources [en-us](https://learn.microsoft.com/en-us/answers/questions/5110518/use-of-exponential-smoothing-formula) [Your Privacy Choices](https://aka.ms/yourcaliforniaprivacychoices) Theme - Light - Dark - High contrast - [AI Disclaimer](https://learn.microsoft.com/en-us/principles-for-ai-generated-content) - [Previous Versions](https://learn.microsoft.com/en-us/previous-versions/) - [Blog](https://techcommunity.microsoft.com/t5/microsoft-learn-blog/bg-p/MicrosoftLearnBlog) - [Contribute](https://learn.microsoft.com/en-us/contribute) - [Privacy](https://go.microsoft.com/fwlink/?LinkId=521839) - [Terms of Use](https://learn.microsoft.com/en-us/legal/termsofuse) - [Code of Conduct](https://aka.ms/msftqacodeconduct) - [Trademarks](https://www.microsoft.com/legal/intellectualproperty/Trademarks/) - © Microsoft 2025
Readable Markdownnull
Shard168 (laksa)
Root Hash14615152987638977768
Unparsed URLcom,microsoft!learn,/en-us/answers/questions/5110518/use-of-exponential-smoothing-formula s443