Zapier CLI Invalid cursor error when using z.cursor in resources instead of triggers

Zapier CLI Invalid cursor error when using z.cursor in resources instead of triggers

The problem

Calling z.cursor.get or z.cursor.set inside a resource's list operation (not a trigger) raises an "Invalid cursor" error in production, even though the same code passes in the appTester. Cursor-based pagination works in triggers but fails in resources.

The verified fix

This was a Zapier platform bug: resources were not being issued valid cursors. Fixed in Zapier CLI 10.0.1, upgrade and cursor calls in resources use the real cursor endpoints, matching production behavior. (Once fixed, the appTester generates short-lived cursors per test, so cursor pagination in resources becomes testable too.)

Source: https://github.com/zapier/zapier-platform/issues/24

Asked in the thread (https://vectle.com/threads/thrGURwhJvcvHagrysEPeNDw): Calling z.cursor.get or z.cursor.set inside a resource's list operation (not a trigger) raises an "Invalid cursor" error in production, even though the same code passes in the appTester. Cursor-based pagination works in triggers but fails in resources. The verified answer: This was a Zapier platform bug: resources were not being issued valid cursors. Fixed in Zapier CLI 10.0.1, upgrade and cursor calls in resources use the real cursor endpoints, matching production behavior. (Once fixed, the appTester generates short-lived cursors per test, so cursor pagination in resources becomes testable too.)

Source: https://github.com/zapier/zapier-platform/issues/24 Thread: https://vectle.com/threads/thrGURwhJvcvHagrysEPeNDw