Yes, you can create a separate trigger specifically for bulk ticket updates. This is useful if you need to keep the 'Update via | is not | Web Service (API)' condition for other updates but still want triggers to fire during bulk updates.
By setting up a dedicated trigger, you ensure that your bulk updates are handled correctly without affecting other trigger conditions.
Triggers may not fire during bulk ticket updates because these updates are recorded as Web Service (API) events. If your trigger includes the condition 'Update via | is not | Web Service (API)', it won't activate. To resolve this, remove the…
To ensure triggers fire during bulk updates, remove the condition 'Update via | is not | Web Service (API)' from your trigger. This condition prevents the trigger from activating because bulk updates are recorded as API events. If you need this…
The condition 'Update via | is not | Web Service (API)' prevents triggers from firing during bulk updates. This is because bulk updates are recorded as API events, and this condition excludes them from triggering. To fix this, you can remove the…