Assume we have a Data Extract Activity in a SFMC Automation workflow. In those activities, you can specify the output filename with date parameters/placeholders:
Enter a file naming pattern so that the activity knows what to name the file it creates. Use when you have set up a workflow to drop a file whose auto-generated filename matches a pattern into the file location. Enter a static name or include placeholders for the date. Use the following personalization strings in your filename: %%Year%% %%Month%% %%Day%% %%Hour%% %%Minute%% %%Second%%
My question is: What timezone is used for those parameters? Is it the BU's timezone? Is it the server timezone of the server running SFMC? Is it some unchangeable default (e.g. always Eastern time)?
Closest question suggests it might be CST (without regard to Daylight savings)? However, it's specifically around an API use case, so I'm not sure if it directly translates.
As an experiment to validate my hunch: I created a Data Extract Activity that included the Hour and Minute wildcards
I ran the activity at 15:30 CDT (CDT is my local timezone in SFMC) and the output file was
filename_2018-06-27--14-30 or 1 hour behind CDT. That means the timezone is either MDT or CST (central time without respecting Daylight savings).
I'm leaning even more towards believing it's CST, but I still don't have a conclusive way of determining that because I don't know if there is a master/BU/other timezone configured in my SFMC instance to MDT or CST. Do those date placeholders obey a specific timezone configured in SFMC or is it always that timezone (MDT/CST) no matter what you do?