Time Now (UTC):
The "Basic data handling: TimeNowUTC" node is designed to provide you with the current date and time in the Coordinated Universal Time (UTC) format. This node is particularly useful when you need a consistent and standardized time reference that is not affected by local time zones or daylight saving changes. By delivering the current UTC time as a DATETIME object, it ensures that you have an accurate and reliable timestamp for your projects, which is crucial for tasks that require synchronization across different geographical locations. The node's output is dynamic, meaning it updates with each execution to reflect the precise moment it is run, making it ideal for real-time applications and logging purposes.
Time Now (UTC) Input Parameters:
trigger
The trigger parameter is an optional input that can be used to initiate the execution of the node. While it does not directly affect the output, it serves as a mechanism to control when the node should generate a new timestamp. This can be particularly useful in workflows where you want to ensure that the time is captured at a specific point in the process. There are no specific minimum, maximum, or default values for this parameter, as it accepts any input to trigger the node's execution.
Time Now (UTC) Output Parameters:
now
The now output parameter provides the current date and time as a DATETIME object in the UTC timezone. This output is crucial for applications that require a universal time reference, ensuring consistency and accuracy across different systems and locations. The DATETIME object includes detailed information such as year, month, day, hour, minute, second, and microsecond, allowing for precise time tracking and logging.
Time Now (UTC) Usage Tips:
- Use the
triggerparameter to control when the node should execute, ensuring that the timestamp is captured at the desired moment in your workflow. - Integrate this node into systems that require synchronization across different time zones to maintain a consistent time reference.
Time Now (UTC) Common Errors and Solutions:
No output generated
- Explanation: This error may occur if the node is not properly triggered.
- Solution: Ensure that the
triggerparameter is correctly set to initiate the node's execution.
Incorrect time format
- Explanation: The output might not be in the expected format if the
DATETIMEobject is not handled correctly in subsequent nodes. - Solution: Verify that the receiving nodes or systems are configured to interpret
DATETIMEobjects correctly, especially in UTC format.
