ur_ingest_session_imap_acct_folder (table) Content

ur_ingest_session_imap_acct_folder (table) Schema


01JTN9WQFS04D5HRK34E1HJKQR	01JTN9TPJXHY2DTBC0E26J5NHM	01JTN9VN46RY6909YDMXA5JPX1	Inbox	{"metadata":"{\n \"id\": \"AAMkADY1MDA5MmMwLTU1YWEtNDMxYy04NmY0LTc2MmJlZDM3NzU4MgAuAAAAAAD3sYY2aa5DRIHeWqpz1aSJAQDIXkyx1KVGQbHbXZIGHMouAAAAAAEMAAA=\",\n \"displayName\": \"Inbox\",\n \"parentFolderId\": \"AAMkADY1MDA5MmMwLTU1YWEtNDMxYy04NmY0LTc2MmJlZDM3NzU4MgAuAAAAAAD3sYY2aa5DRIHeWqpz1aSJAQDIXkyx1KVGQbHbXZIGHMouAAAAAAEIAAA=\",\n \"childFolderCount\": 0,\n \"unreadItemCount\": 42632,\n \"totalItemCount\": 42734,\n \"sizeInBytes\": 2996872379,\n \"isHidden\": false\n}"}	2025-05-07 12:00:27	system
01JXKTE2EPBAN8C2EB0A1V1672	01JXKT7KRHPTHP2EW8PV65QBMS	01JXKTBJ7MVHGV0JF6DR37X6A2	Inbox	{"metadata":"{\n \"id\": \"AAMkADY1MDA5MmMwLTU1YWEtNDMxYy04NmY0LTc2MmJlZDM3NzU4MgAuAAAAAAD3sYY2aa5DRIHeWqpz1aSJAQDIXkyx1KVGQbHbXZIGHMouAAAAAAEMAAA=\",\n \"displayName\": \"Inbox\",\n \"parentFolderId\": \"AAMkADY1MDA5MmMwLTU1YWEtNDMxYy04NmY0LTc2MmJlZDM3NzU4MgAuAAAAAAD3sYY2aa5DRIHeWqpz1aSJAQDIXkyx1KVGQbHbXZIGHMouAAAAAAEIAAA=\",\n \"childFolderCount\": 0,\n \"unreadItemCount\": 44522,\n \"totalItemCount\": 44624,\n \"sizeInBytes\": 3738915402,\n \"isHidden\": false\n}"}	2025-06-13 04:58:09	system

Error We are sorry, but an error occurred while generating this page. You should contact the site's administrator.

Error in query number 6:

Parsing failed: SQLPage couldn't understand the SQL file. Please check for syntax errors:

            SELECT 'text' AS component,
                (SELECT CASE WHEN $current_page > 1 THEN '[Previous](?limit=' || $limit || '&offset=' || ($offset - $limit) || ')' ELSE ' END) || ' ' ||
                                 ⬆️
                '(Page ' || $current_page || ' of ' || $total_pages || ') ' ||

Backtrace

sql parser error: Expected: ), found: $current_page at Line: 42, Column: 35

"console/content/table/ur_ingest_session_imap_acct_folder.auto.sql" contains a syntax error preventing SQLPage from parsing and preparing its SQL statements.

You can hide error messages like this one from your users by setting the 'environment' configuration option to 'production'.