ContributionsMost RecentMost LikesSolutionsRe: Setting Time Stamp with API_EditRecord Using Epoch MillisecondsThanks, Nathan, that is very helpful. --Jeffrey ------------------------------ Ad Planner System Technical Solutions Specialist RR Donnelley ------------------------------ Setting Time Stamp with API_EditRecord Using Epoch MillisecondsI can successfully set a time stamp value using API_EditRecord by supplying a number of milliseconds since 01-01-1970. This is a 13-digit integer, generated from a 10-digit epoch time (seconds) provided by my operating system, multiplied by 1000. My users are in the United States Central Time Zone, and my app is configured to display times as US Central Time. US Central Standard Time is six hours "behind" Coordinated Universal Time (UTC). When I update the time stamp using a US Central Time epoch milliseconds value, my app displays a time six hours in the future. For example if I set the time to be 12-30-2020 3:15:00 PM, it's displayed in the app as 12-30-2020 9:15:00 PM. If I subtract six hours from the time stamp I actually want to use, the time is displayed appropriately in my app. Can anyone confirm that this is the expected behavior, and that my time stamp value requires a time zone offset (-6 hours, or -5 for Daylight Savings Time) in order to display correctly in my app? Thanks for reading ... ------------------------------ Ad Planner System Admin Technical Solutions Specialist RR Donnelley ------------------------------Token Expires During Overnight QB AutomationsWe have several automations that run overnight -- mainly table imports -- and some of the automations have a sequence of several actions. They all run as a user with full permissions to everything within the app. Sometimes an Automation action fails, and an email from Quick Base states: Insufficient permissions, You don't have permission to access that pageAuthorization token is expired. In the Automations dashboard, the error details for the failed action state: Insufficient permissions, You don't have permission to access that pageAuthorization token is expired.: Loop Index: 1; Failed on Step: Run table-to-table import (ID: step_5b538eb048c211ea8c1893f53b32fb48a); How can I avoid these failures? I don't explicitly request/use a token, it's all just driven by QB internal Automation. ------------------------------ Ad Planner System, aka Jeffrey Pierce ------------------------------