Which event is NOT a trigger for notifications?

User login is not typically considered a trigger for notifications in ServiceNow. Notifications in ServiceNow are designed to respond to specific changes or actions within a record or system events.

When a record is inserted or updated, or when a specific event is fired, these actions can activate notifications to inform users about changes or occurrences relevant to their roles or responsibilities. For example, record inserts or updates serve as straightforward triggers for notifications, notifying stakeholders when items are newly added or altered. Similarly, events fired in the system can be configured to trigger notifications based on predefined conditions.

While scripts can be designed to trigger notifications based on custom conditions or to perform actions that include notifying users, the mechanics of the script itself are not inherently a notification trigger unless explicitly programmed as such.

User logins, on the other hand, are primarily used for access control and session management within the application, rather than content change notifications. Therefore, this event does not directly correlate with the functionality of triggering notifications in ServiceNow, making it the correct answer.