|
25858
|
Unnamed Group
TypeError: League\Flysystem\Filesyst Unnamed Group
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
CloudWatch | us-east-2
CloudWatch | us-east-2
Close tab
Pipelines - jiminny/app
Pipelines - jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking for automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking for automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
[SRD-6793] Les Mills activity types not pulling in - Jira
[SRD-6793] Les Mills activity types not pulling in - Jira
Platform Team - Backlog - Jira
Platform Team - Backlog - Jira
Userpilot | Events
Userpilot | Events
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AWS Console Home
Skip to Main Content
Skip to Main Content
Amazon Q
Services
Search
Ask Amazon Q
[Option+S]
CloudShell
Notifications (none available)
Help & support
Settings
United States (Ohio)
United States (Ohio)
PROD
Account ID: 4103-4619-5943
PROD
EC2 EC2
EC2
Elastic Container Service Elastic Container Service
Elastic Container Service
S3 S3
S3
CodeDeploy CodeDeploy
CodeDeploy
CloudWatch CloudWatch
CloudWatch
ElastiCache ElastiCache
ElastiCache
Aurora and RDS Aurora and RDS
Aurora and RDS
Amazon OpenSearch Service Amazon OpenSearch Service
Amazon OpenSearch Service
CloudFront CloudFront
CloudFront
MediaLive MediaLive
MediaLive
Open side navigation
CloudWatch
CloudWatch
Logs Insights
Logs Insights
Query definition
Query definition
Info : Query definition
Log Analytics
a unified observability platform for a smoother experience, now in preview mode. Click
here
here
to try it out!
5m (5 Minutes)
30m (30 Minutes)
1h (1 Hour)
3h (3 Hours)
12h (12 Hours)
Custom
Custom
Compare (Off)
Compare
(
Off
)
Time zone UTC timezone
UTC timezone
Start tailing with selected log group (opens in a new tab)
Start tailing
Query scope
Query scope All log groups
All log groups
All log groups
Log class
Log class STANDARD
STANDARD
Account(s)
Account(s) Change Account(s)
Change Account(s)
Remove All accounts
Undo
Redo
Logs Insights QL
Query generator
Query generator
Fields
Saved and sample queries
Query commands
Run query
Cancel
Save
History
Completed. Query executed for
78 log groups.
View log groups used in query
Logs (2)
Logs
(
2
)
Patterns (2)
Patterns
(
2
)
Visualization
Visualization
Logs (2)...
|
Firefox
|
CloudWatch | us-east-2 — Work
|
us-east-2.console.aws.amazon.com/cloudwatch/home?r us-east-2.console.aws.amazon.com/cloudwatch/home?region=us-east-2#logsV2:logs-insights$3FqueryDetail$3D~(end~0~start~-43200~timeType~'RELATIVE~tz~'UTC~unit~'seconds~editorString~'fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fb1c6e693-0843-4d6d-a43e-633969a3541e*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000~queryId~'0551e814-f51a-4339-8372-80d7ba4cef27~source~(~'*2a)~lang~'CWLI~logClass~'STANDARD~accountIDs~(~'All)~queryBy~'allLogGroups)...
|
25858
|
|
24084
|
SlackFileEditViewGoHistoryWindowHelpDOCKERDOCKER ( SlackFileEditViewGoHistoryWindowHelpDOCKERDOCKER (-zsh)₴81DEV (-zsh)О 882APP (-zsh)883EU ()-zshasticsearch"{"type" : "log""@timestamp": "2026-05-11T19:54:53Z","tags" : ["warning""el,"data"], "pid" :7,'"message": "Unablerevive connection: [URL_WITH_CREDENTIALS] : "2026-05-11T19:54:532",: ["warning".asticsearch", "data"],"pid":7,"message": "No livingconnections "}I {"type" : "log", "@timestamp" : "2026-05-11T19:54:53Z""tags" : ["warning""licensing"], "pid" :7,"message" : "License informationcould not be obtained from Elasticsearch due to Error: No Livingconnectionskibana1 {"type" : "log","@timestamp": "2026-05-11T19:54:54Z","tags" : ["error"ticsearch", "data"], "pid":7, "message" : "[ConnectionError]: getaddrinfo ENOTFOUND elasticsearch elasticsearch: 9200"}kibana1 {"type" : "log","@timestamp" : "2026-05-11T19:54:54Z", "tags" : ["warning", "elasticsearch", "data"], "pid" :7,"message":"Unable to revive connection: [URL_WITH_CREDENTIALS] "2026-05-11T19:54:54Z", "tags" : ["warning", "elasticsearch", "data"],"pid":7,"message"• "No livingconnections"}kibana1 {"type": "1og","@timestamp": "2026-05-11T19:54:54Z","tags": ["error","plugins", "taskManager""taskManager"], "pid":7, "message": "Failed to poll for work: Error: NoLiving connections"}kibana1 {"type": "log", "@timestamp": "2026-05-11T19:54:57Z", "tags" : ["error","elasticsearch".,"data"], "pid" :7, "message" :"[ConnectionError]: getaddrinfo ENOTFOUND elasticsearch elasticsearch:9200*}kibana1 {"type" : "Log","@timestamp" : "2026-05-11T19:54:57Z","tags" : ["warning", "elasticsearch", "data"], "pid" :7, "message": "Unable to revive connection: [URL_WITH_CREDENTIALS] : "2026-05-11T19:54:57Z", "tags" : ["warning", "elasticsearch", "data"], "pid" :7, "message": "No living connections"}kibanaI {"type" : "log", "@timestamp" : "2026-05-11T19:54:57Z", "tags" : ["error"ins","taskManager", "taskManager"], "pid":7, "message": "Failed to poll for work: Error: NoLiving connections"}kibanaI {"type" : "log", "@timestamp" : "2026-05-11T19:54:59Z""tags" : ["error", "elasticsearch", "data"], "pid" :7, "message" : "[ConnectionError]: getaddrinfo ENOTFOUND elasticsearch elasticsearch:9200"}1 {"type" : "log","@timestamp" : "2026-05-11T19:55: 00Z","tags" : ["warning"asticsearch", "data"], "pid" :7, "message": "Unable to revive connection: [URL_WITH_CREDENTIALS] : "2026-05-11T19:55:00Z", "tags" : ["warning", "elasticsearch", "data"], "pid" :7, "message": "No living connections"}1 {"type": "log", "@timestamp": "2026-05-11T19:55:00Z", "tags" : ["error", "plug, "taskManager",, "taskManager"], "pid" :7, "message" : "Failed to poll for work: Error: NoLiving connections"}unexpected EOFkas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/infrastructure/dev/docker (develop) $HomeDMsActivityFilesLaterMoreallSupport Daily - in 3 h 17 m100% C3• Tue 12 May 11:43:01→Describe what you are looking forJiminny ...# support8 346 0& jiminny-x-integrati...& platform-inner-team• MessagesBookmarksMore v+# Channels# ai-chapter# alerts# backend# bugs# confusion-clinic# curiosity_lab#engineeringMore88ToolsCreate and find workflows and appsCustomize navigation bar# sofia-office# support# thank-yous# the_people_of jimi...^ Direct messages&. Petko KashinskiRo Steliyan Georgiev. Galya Dimitrovae. Aneliya Angelovaa. Stefka Stoyanova€. Vasil VasilevC Filessome old corru'Yesterday~ ied the process, andmassively delayed it.A few fixes were applied. I have increased thenumber of servers consuming activities, but it willstill take some time until all scheduled activities areprocessed and indexed.What that means - we were processing older data(since Jan 1st 26) but those activities compete withfreshly imported calls and conversations. And newcalls and conversations may be delayed a bit.Apart from the delay not issues with new activitiesara aynerted.m happened only on EU, all US datawas finished over the weekend.* 3Today ~vasll vasilev 11:38 AMAll EU data is reindexed.But it turned out that the US is still in progress. Itwas reported the indexing has finished over theweekend, but apparently it's not. I've increased thenumber of consumers, that should speed up theremaining data consumption. Some delays mayhappen until all data indexing is finished.H1Message #support+...
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24084
|
|
24086
|
New Tab
New Tab
TypeError: League\Flysystem\Filesy New Tab
New Tab
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app...
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24086
|
|
24087
|
SlackFileEditViewGoHistoryWindowHelpDOCKERDOCKER ( SlackFileEditViewGoHistoryWindowHelpDOCKERDOCKER (-zsh)₴81DEV (-zsh)O $2APP (-zsh)883EU ()-zshasticsearch"{"type" : "log""@timestamp": "2026-05-11T19:54:53Z","tags" : ["warning""el,"data"], "pid" :7,'"message": "Unablerevive connection: [URL_WITH_CREDENTIALS] : "2026-05-11T19:54:532",: ["warning".asticsearch", "data"],"pid":7,"message": "No livingconnections "}I {"type" : "log", "@timestamp" : "2026-05-11T19:54:53Z""tags" : ["warning""licensing"], "pid" :7,"message" : "License informationcould not be obtained from Elasticsearch due to Error: No Livingconnectionskibana1 {"type" : "log","@timestamp": "2026-05-11T19:54:54Z","tags" : ["error"ticsearch", "data"], "pid":7, "message" : "[ConnectionError]: getaddrinfo ENOTFOUND elasticsearch elasticsearch: 9200"}kibana1 {"type" : "log","@timestamp" : "2026-05-11T19:54:54Z", "tags" : ["warning", "elasticsearch", "data"], "pid" :7,"message":"Unable to revive connection: [URL_WITH_CREDENTIALS] "2026-05-11T19:54:54Z", "tags" : ["warning", "elasticsearch", "data"],"pid":7,"message"• "No livingconnections"}kibana1 {"type": "1og","@timestamp": "2026-05-11T19:54:54Z","tags": ["error","plugins", "taskManager""taskManager"], "pid":7, "message": "Failed to poll for work: Error: NoLiving connections"}kibana1 {"type": "log", "@timestamp": "2026-05-11T19:54:57Z", "tags" : ["error","elasticsearch".,"data"], "pid" :7, "message" :"[ConnectionError]: getaddrinfo ENOTFOUND elasticsearch elasticsearch:9200*}kibana1 {"type" : "Log","@timestamp" : "2026-05-11T19:54:57Z","tags" : ["warning", "elasticsearch", "data"], "pid" :7, "message": "Unable to revive connection: [URL_WITH_CREDENTIALS] : "2026-05-11T19:54:57Z", "tags" : ["warning", "elasticsearch", "data"], "pid" :7, "message": "No living connections"}kibanaI {"type" : "log", "@timestamp" : "2026-05-11T19:54:57Z", "tags" : ["error"ins","taskManager", "taskManager"], "pid":7, "message": "Failed to poll for work: Error: NoLiving connections"}kibanaI {"type" : "log", "@timestamp" : "2026-05-11T19:54:59Z""tags" : ["error", "elasticsearch", "data"], "pid" :7, "message" : "[ConnectionError]: getaddrinfo ENOTFOUND elasticsearch elasticsearch:9200"}kibana1 {"type" : "log","@timestamp" : "2026-05-11T19:55: 00Z","tags" : ["warning", "elasticsearch", "data"], "pid" :7, "message": "Unable to revive connection: [URL_WITH_CREDENTIALS] : "2026-05-11T19:55:00Z", "tags" : ["warning", "elasticsearch", "data"], "pid" :7, "message": "No living connections"}1 {"type": "log", "@timestamp": "2026-05-11T19:55:00Z", "tags" : ["error", "plug, "taskManager",, "taskManager"], "pid" :7, "message" : "Failed to poll for work: Error: NoLiving connections"}unexpected EOFkas@Lukas-Kovaliks-MacBook-Pro-Jiminny ~/jiminny/infrastructure/dev/docker (develop) $HomeDMsActivityFilesLaterMoreallSupport Daily - in 3 h 17 m100% C3• Tue 12 May 11:43:04→Describe what you are looking forJiminny ...# support8 346 0& jiminny-x-integrati...& platform-inner-team• MessagesBookmarksMore v+# Channels# ai-chapter# alerts# backend# bugs# confusion-clinic# curiosity_lab#engineeringMore88ToolsCreate and find workflows and appsCustomize navigation bar# sofia-office# support# thank-yous# the_people_of jimi...^ Direct messages&. Petko KashinskiRo Steliyan Georgiev. Galya Dimitrovae. Aneliya Angelovaa. Stefka Stoyanova€. Vasil VasilevC Filessome old corru'Yesterday~ ied the process, andmassively delayed it.A few fixes were applied. I have increased thenumber of servers consuming activities, but it willstill take some time until all scheduled activities areprocessed and indexed.What that means - we were processing older data(since Jan 1st 26) but those activities compete withfreshly imported calls and conversations. And newcalls and conversations may be delayed a bit.Apart from the delay not issues with new activitiesara aynerted.m happened only on EU, all US datawas finished over the weekend.* 3Today ~vasll vasilev 11:38 AMAll EU data is reindexed.But it turned out that the US is still in progress. Itwas reported the indexing has finished over theweekend, but apparently it's not. I've increased thenumber of consumers, that should speed up theremaining data consumption. Some delays mayhappen until all data indexing is finished.H1Message #support+...
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24087
|
|
24088
|
New Tab
New Tab
TypeError: League\Flysystem\Filesy New Tab
New Tab
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Close tab
Jiminny
Jiminny
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account
Remember this account
IAM username
[EMAIL]
Password
[PASSWORD_DOTS]
Show Password
Show Password
Having trouble?
Having trouble?
Sign in
Sign in using root user email
Create a new AWS account
By continuing, you agree to
AWS Customer Agreement
AWS Customer Agreement
or other agreement for AWS services, and the
Privacy Notice
Privacy Notice
. This site uses essential cookies. See our
Cookie Notice
Cookie Notice
for more information.
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24088
|
|
24089
|
New Tab
about:home
New Tab
New Tab
Close tab
Amazo New Tab
about:home
New Tab
New Tab
Close tab
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account
Remember this account
IAM username
[EMAIL]
Password
[PASSWORD_DOTS]
Show Password
Show Password
Having trouble?
Having trouble?
Sign in
Sign in using root user email
Create a new AWS account
By continuing, you agree to
AWS Customer Agreement
AWS Customer Agreement
or other agreement for AWS services, and the
Privacy Notice
Privacy Notice
. This site uses essential cookies. See our
Cookie Notice
Cookie Notice
for more information.
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24089
|
|
24090
|
New Tab
about:home
New Tab
New Tab
Close tab
Amazo New Tab
about:home
New Tab
New Tab
Close tab
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account
Remember this account
IAM username
[EMAIL]
Password
[PASSWORD_DOTS]
Show Password
Show Password
Having trouble?
Having trouble?
Sign in
Sign in using root user email
Create a new AWS account
By continuing, you agree to
AWS Customer Agreement
AWS Customer Agreement
or other agreement for AWS services, and the
Privacy Notice
Privacy Notice
. This site uses essential cookies. See our
Cookie Notice
Cookie Notice
for more information.
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24090
|
|
24091
|
Amazon Web Services Sign-In
us-east-2.signin.aws.a Amazon Web Services Sign-In
us-east-2.signin.aws.amazon.com
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account
Remember this account
IAM username
[EMAIL]
Password
[PASSWORD_DOTS]
Show Password
Show Password
Having trouble?
Having trouble?
Sign in
Sign in using root user email
Create a new AWS account
By continuing, you agree to
AWS Customer Agreement
AWS Customer Agreement
or other agreement for AWS services, and the
Privacy Notice
Privacy Notice
. This site uses essential cookies. See our
Cookie Notice
Cookie Notice
for more information.
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24091
|
|
24092
|
Amazon Web Services Sign-In
us-east-2.signin.aws.a Amazon Web Services Sign-In
us-east-2.signin.aws.amazon.com
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account
Remember this account
IAM username
[EMAIL]
Password
[PASSWORD_DOTS]
Show Password
Show Password
Having trouble?
Having trouble?
Sign in
Sign in using root user email
Create a new AWS account
By continuing, you agree to
AWS Customer Agreement
AWS Customer Agreement
or other agreement for AWS services, and the
Privacy Notice
Privacy Notice
. This site uses essential cookies. See our
Cookie Notice
Cookie Notice
for more information.
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24092
|
|
24093
|
TypeError: League\Flysystem\Filesystem::has(): Arg TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Unnamed Group
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account...
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24093
|
|
24094
|
TypeError: League\Flysystem\Filesystem::has(): Arg TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Unnamed Group
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account
Remember this account
IAM username
[EMAIL]
Password
[PASSWORD_DOTS]
Show Password
Show Password
Having trouble?
Having trouble?
Sign in
Sign in using root user email
Create a new AWS account
By continuing, you agree to
AWS Customer Agreement
AWS Customer Agreement
or other agreement for AWS services, and the
Privacy Notice
Privacy Notice
. This site uses essential cookies. See our
Cookie Notice
Cookie Notice
for more information.
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24094
|
|
24102
|
Unnamed Group
TypeError: League\Flysystem\Filesyst Unnamed Group
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
Unnamed Group
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account
Remember this account
IAM username
[EMAIL]
Password
[PASSWORD_DOTS]
Show Password
Show Password
Having trouble?
Having trouble?
Sign in
Sign in using root user email
Create a new AWS account
By continuing, you agree to
AWS Customer Agreement
AWS Customer Agreement
or other agreement for AWS services, and the
Privacy Notice
Privacy Notice
. This site uses essential cookies. See our
Cookie Notice
Cookie Notice
for more information.
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24102
|
|
24103
|
Unnamed Group
TypeError: League\Flysystem\Filesyst Unnamed Group
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
Unnamed Group
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Multi-session disabled
Multi-session disabled
Language English
English
Amazon Web Services logo
IAM user sign in
IAM user sign in
Account ID or alias
(Don't have?)
(Don't have?)
jmny
Remember this account
Remember this account
IAM username
[EMAIL]
Password
[PASSWORD_DOTS]
Show Password
Show Password
Having trouble?
Having trouble?
Sign in
Sign in using root user email
Create a new AWS account
By continuing, you agree to
AWS Customer Agreement
AWS Customer Agreement
or other agreement for AWS services, and the
Privacy Notice
Privacy Notice
. This site uses essential cookies. See our
Cookie Notice
Cookie Notice
for more information.
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24103
|
|
24104
|
Unnamed Group
TypeError: League\Flysystem\Filesyst Unnamed Group
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
Unnamed Group
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Language English
English
Amazon Web Services logo
Additional verification required
Additional verification required
Your account is protected with
multi-factor authentication
(MFA)
(MFA)
.
To finish signing in, enter the code from your MFA device below
.
MFA code
MFA code
Sign in
Sign in to a different account
Trouble signing in?
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24104
|
|
24108
|
Unnamed Group
TypeError: League\Flysystem\Filesyst Unnamed Group
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Amazon Web Services Sign-In
Amazon Web Services Sign-In
Close tab
Unnamed Group
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
Data Explorer
Data Explorer
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
Jiminny
Jiminny
New Tab
Customize sidebar
Open Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
Provide feedback
Language English
English
Amazon Web Services logo
Additional verification required
Additional verification required
Your account is protected with
multi-factor authentication
(MFA)
(MFA)
.
To finish signing in, enter the code from your MFA device below
.
MFA code
694975
Sign in
Sign in to a different account
Trouble signing in?
Amazon Web Services Marketing
©
2026
Amazon Web Services, Inc. or its affiliates. All rights reserved....
|
Firefox
|
Amazon Web Services Sign-In — Work
|
us-east-2.signin.aws.amazon.com/oauth?client_id=ar us-east-2.signin.aws.amazon.com/oauth?client_id=arn%3Aaws%3Asignin%3A%3A%3Aconsole%2Fcloudwatch&code_challenge=M9tQp-WiEnPJPpKZmLVj5TYzHdkFR84sQNa8N91GBqM&code_challenge_method=SHA-256&response_type=code&redirect_uri=https%3A%2F%2Fus-east-2.console.aws.amazon.com%2Fcloudwatch%2Fhome%3Fca-oauth-flow-id%3D0c5f%26hashArgs%3D%2523logsV2%253Alogs-insights%25243FqueryDetail%25243D%257E%2528end%257E0%257Estart%257E-3600%257EtimeType%257E%2527RELATIVE%257Etz%257E%2527UTC%257Eunit%257E%2527seconds%257EeditorString%257E%2527fields*20*40timestamp*2c*20*40message*2c*20*40logStream*2c*20*40log*0a*7c*20filter*20*40message*20like*20*2fXXXXX*2f*20*0a*7c*20filter*20*40message*20not*20like*20*2fAnalytic*2f*20*7c*20filter*20*40message*20not*20like*20*2fTranscript*2f*0a*7c*20filter*20*40message*20not*20like*20*2fWebhook*2f*20*7c*20filter*20*40message*20not*20like*20*2fMeetingBot*2f*20*0a*7c*20limit*2010000%257EqueryId%257E%25270551e814-f51a-4339-8372-80d7ba4cef27%257Esource%257E%2528%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-analytics%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-audio%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-calendar%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-conferences%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-crm-sync%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-default%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-dialers-fifo%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-download%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-emails%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-meeting-bot%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-nudges%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-1%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-2%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-3%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-4%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-5%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-processing-delayed%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-softphone%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aworker-video-app%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp%257E%2527arn*3aaws*3alogs*3aus-east-2*3a410346195943*3alog-group*3aphp-app%2529%257Elang%257E%2527CWLI%257ElogClass%257E%2527STANDARD%257EqueryBy%257E%2527logGroupName%2529%26isauthcode%3Dtrue%26oauthStart%3D1778575381333%26region%3Dus-east-2%26state%3DhashArgsFromTB_us-east-2_1aac6e50d788b437...
|
24108
|
|
22642
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Planhat
Planhat
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings...
|
Firefox
|
Planhat — Work
|
ws.planhat.com
|
22642
|
|
22709
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Login
Login
Planhat
Planhat
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page...
|
Firefox
|
Planhat — Work
|
ws.planhat.com
|
22709
|
|
22723
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Close tab
Login
Login
New Tab...
|
Firefox
|
Planhat — Work
|
ws.planhat.com
|
22723
|
|
22724
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted...
|
Firefox
|
Planhat — Work
|
ws.planhat.com
|
22724
|
|
22652
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Planhat
Planhat
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Show thinking
Gemini said
Gemini said
Here is a summary of the changes in the provided code diff:
AI Call Scoring Additions
AI Call Scoring Additions
Pre-computed Scores:
Added strict instructions to treat the
ai_call_score
as pre-computed data. The system must interpret and summarize the provided scores rather than inventing or recalculating them.
Context Breakdown:
*
Short Context:
Now displays the
AI Scorecard
name and the overall
AI Score
(the average of per-rule scores).
Full Context:
Details the
ai_call_score
object, breaking down individual rules. Each rule includes a title, prompt, a 1–5 score, a brief justification, and up to three timestamped speaker references (MM:SS).
Application Rules:
Instructs the system to use these scores for coaching summaries, trends, and comparisons, but dictates that it must still rely on the actual transcript for direct quotes.
Grammar and Formatting Cleanup
Grammar and Formatting Cleanup
Typo Corrections:
Fixed minor grammatical errors, such as changing "contexts" to "context" and "utlizes" to "utilizes".
String Formatting:
Cleaned up the markdown link instructions by removing trailing newline and quotation artifacts (
\n"
) from the text strings.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said are there some issues and bottlenecks
You said
are there some issues and bottlenecks
Listen
Show thinking
Gemini said
Gemini said
Looking closely at the system instructions in the diff, there are definitely a few potential prompt engineering issues and bottlenecks introduced by these additions. When you ask a Large Language Model (LLM) to juggle large transcripts alongside complex JSON scoring objects, it creates specific friction points.
Here is a breakdown of the potential issues and bottlenecks based on the changes:
1. Token Consumption and Context Bloat (Bottleneck)
1. Token Consumption and Context Bloat (Bottleneck)
Massive Payload Size:
By injecting the full
ai_call_score
object into the context (which includes rule names, prompts, scores, text justifications, and up to three timestamps
per rule
), the token count per call will skyrocket.
Context Window Limits:
The prompt states:
"The full call context includes all calls data available..."
If a user filters for 5 or 10 calls, injecting the transcripts
plus
these extensive AI scoring arrays could easily hit the model's maximum context window, leading to truncated data or degraded recall (the "lost in the middle" effect).
2. LLM Instruction Conflicts (Issue)
2. LLM Instruction Conflicts (Issue)
Pre-computed vs. Raw Transcript:
The prompt explicitly instructs the model:
"
Do not
invent, override, or recalculate scores"
but later says,
"For
what was actually said
, still rely on the
transcript
."
This creates a cognitive conflict for the LLM. If the raw transcript contradicts the pre-computed
justification
, the LLM might struggle with which source of truth to prioritize, potentially leading to hallucinations or contradictory summaries.
Prompt Complexity:
The more rules you add about
how
to read JSON formatting and
what
not to do, the less attention the model pays to the actual user query. This is a common bottleneck in prompt engineering known as instruction bloat.
3. Edge Cases in Formatting (Issue)
3. Edge Cases in Formatting (Issue)
Timestamp Limitations:
The instructions strictly define timestamps as
MM:SS
. This works fine for standard calls, but for longer meetings (over an hour), it either forces an awkward format (e.g.,
85:30
) or breaks if the system outputs
HH:MM:SS
.
Decimal vs. Whole Numbers:
The prompt specifies that the overall AI Score might be a decimal (average), but the individual rule score is a "Whole number
1–5
". If the upstream pipeline accidentally passes a decimal for a rule score, the LLM might get confused based on these rigid instructions.
How are you currently handling pagination or chunking for these calls—are you limiting the number of calls that can be passed into the full context at once to avoid token limits?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page...
|
Firefox
|
Planhat — Work
|
ws.planhat.com/jiminny
|
22652
|
|
22711
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app...
|
Firefox
|
Login — Work
|
ws.planhat.com/jiminny
|
22711
|
|
22712
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app...
|
Firefox
|
Login — Work
|
ws.planhat.com/jiminny
|
22712
|
|
22713
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
QuickTime PlayerFileEditViewWindowHelp> 0.(aholSupport Daily - in 4 h 41 m• PLanhat Petko interest event 2026-05-11.mp4Screen snareChromeFileEditViewHistoryBookmarksProfilesTabWindowHelpQNGreetiScorecandrejf wilsonCall ArJiminnM Inbox=Nate R= Aр®BuildirUserpws.planhat.com/jiminny/apps?id=66ceb97643c2530bb32c8bb6АIKB• ChatPlayground Al....Jiminny - Calenda...M GMailMy Calendly - Eve...= PH New UI LoginGet Starting with J...AppsChloe Onboarding.+ CX Journey SMB....+ BackSearch Jiminny83 App Center& UP > PH UXE All apps& Created by meG Recentiy most activeIntegrations8 AutomationsP Private apps0 EditorPa Runs8 Data100% C78• Tue 12 May 10:19:018•Mon 11 May 12:17New te+f Work40 +. Petko•** XEnabled4 Webhook incomingA WebhookWebhookEvent details8bcea7d0-160b- @TriggeranythingOmsTriggered by& Support User (Removed)6 Huddle with Lukas KovalikEa Event log9= Al Notes: Off00:07-I04:55app_token*:*data*: ("NX-9946e170",7&+Leav...
|
Firefox
|
Planhat — Work
|
ws.planhat.com/jiminny
|
22713
|
|
22725
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Planhat
Planhat
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?...
|
Firefox
|
Planhat — Work
|
ws.planhat.com/jiminny
|
22725
|
|
22758
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Apps
Apps
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone...
|
Firefox
|
Apps — Work
|
ws.planhat.com/jiminny
|
22758
|
|
22653
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Home
Home
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Show thinking
Gemini said
Gemini said
Here is a summary of the changes in the provided code diff:
AI Call Scoring Additions
AI Call Scoring Additions
Pre-computed Scores:
Added strict instructions to treat the
ai_call_score
as pre-computed data. The system must interpret and summarize the provided scores rather than inventing or recalculating them.
Context Breakdown:
*
Short Context:
Now displays the
AI Scorecard
name and the overall
AI Score
(the average of per-rule scores).
Full Context:
Details the
ai_call_score
object, breaking down individual rules. Each rule includes a title, prompt, a 1–5 score, a brief justification, and up to three timestamped speaker references (MM:SS).
Application Rules:
Instructs the system to use these scores for coaching summaries, trends, and comparisons, but dictates that it must still rely on the actual transcript for direct quotes.
Grammar and Formatting Cleanup
Grammar and Formatting Cleanup
Typo Corrections:
Fixed minor grammatical errors, such as changing "contexts" to "context" and "utlizes" to "utilizes".
String Formatting:
Cleaned up the markdown link instructions by removing trailing newline and quotation artifacts (
\n"
) from the text strings.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said are there some issues and bottlenecks
You said
are there some issues and bottlenecks
Listen
Show thinking
Gemini said
Gemini said
Looking closely at the system instructions in the diff, there are definitely a few potential prompt engineering issues and bottlenecks introduced by these additions. When you ask a Large Language Model (LLM) to juggle large transcripts alongside complex JSON scoring objects, it creates specific friction points.
Here is a breakdown of the potential issues and bottlenecks based on the changes:
1. Token Consumption and Context Bloat (Bottleneck)
1. Token Consumption and Context Bloat (Bottleneck)
Massive Payload Size:
By injecting the full
ai_call_score
object into the context (which includes rule names, prompts, scores, text justifications, and up to three timestamps
per rule
), the token count per call will skyrocket.
Context Window Limits:
The prompt states:
"The full call context includes all calls data available..."
If a user filters for 5 or 10 calls, injecting the transcripts
plus
these extensive AI scoring arrays could easily hit the model's maximum context window, leading to truncated data or degraded recall (the "lost in the middle" effect).
2. LLM Instruction Conflicts (Issue)
2. LLM Instruction Conflicts (Issue)
Pre-computed vs. Raw Transcript:
The prompt explicitly instructs the model:
"
Do not
invent, override, or recalculate scores"
but later says,
"For
what was actually said
, still rely on the
transcript
."
This creates a cognitive conflict for the LLM. If the raw transcript contradicts the pre-computed
justification
, the LLM might struggle with which source of truth to prioritize, potentially leading to hallucinations or contradictory summaries.
Prompt Complexity:
The more rules you add about
how
to read JSON formatting and
what
not to do, the less attention the model pays to the actual user query. This is a common bottleneck in prompt engineering known as instruction bloat.
3. Edge Cases in Formatting (Issue)
3. Edge Cases in Formatting (Issue)
Timestamp Limitations:
The instructions strictly define timestamps as
MM:SS
. This works fine for standard calls, but for longer meetings (over an hour), it either forces an awkward format (e.g.,
85:30
) or breaks if the system outputs
HH:MM:SS
.
Decimal vs. Whole Numbers:
The prompt specifies that the overall AI Score might be a decimal (average), but the individual rule score is a "Whole number
1–5
". If the upstream pipeline accidentally passes a decimal for a rule score, the LLM might get confused based on these rigid instructions.
How are you currently handling pagination or chunking for these calls—are you limiting the number of calls that can be passed into the full context at once to avoid token limits?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications
More
More
Sections
Sections
CS Day-to-day
🚀 Getting started Guide
🪬 Just CS Data
👉 Daily Operations
🗓️ Weekly prep
🤑 Renewals and Upsell...
|
Firefox
|
Home — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22653
|
|
22654
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Show thinking
Gemini said
Gemini said
Here is a summary of the changes in the provided code diff:
AI Call Scoring Additions
AI Call Scoring Additions
Pre-computed Scores:
Added strict instructions to treat the
ai_call_score
as pre-computed data. The system must interpret and summarize the provided scores rather than inventing or recalculating them.
Context Breakdown:
*
Short Context:
Now displays the
AI Scorecard
name and the overall
AI Score
(the average of per-rule scores).
Full Context:
Details the
ai_call_score
object, breaking down individual rules. Each rule includes a title, prompt, a 1–5 score, a brief justification, and up to three timestamped speaker references (MM:SS).
Application Rules:
Instructs the system to use these scores for coaching summaries, trends, and comparisons, but dictates that it must still rely on the actual transcript for direct quotes.
Grammar and Formatting Cleanup
Grammar and Formatting Cleanup
Typo Corrections:
Fixed minor grammatical errors, such as changing "contexts" to "context" and "utlizes" to "utilizes".
String Formatting:
Cleaned up the markdown link instructions by removing trailing newline and quotation artifacts (
\n"
) from the text strings.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said are there some issues and bottlenecks
You said
are there some issues and bottlenecks
Listen
Show thinking
Gemini said
Gemini said
Looking closely at the system instructions in the diff, there are definitely a few potential prompt engineering issues and bottlenecks introduced by these additions. When you ask a Large Language Model (LLM) to juggle large transcripts alongside complex JSON scoring objects, it creates specific friction points.
Here is a breakdown of the potential issues and bottlenecks based on the changes:
1. Token Consumption and Context Bloat (Bottleneck)
1. Token Consumption and Context Bloat (Bottleneck)
Massive Payload Size:
By injecting the full
ai_call_score
object into the context (which includes rule names, prompts, scores, text justifications, and up to three timestamps
per rule
), the token count per call will skyrocket.
Context Window Limits:
The prompt states:
"The full call context includes all calls data available..."
If a user filters for 5 or 10 calls, injecting the transcripts
plus
these extensive AI scoring arrays could easily hit the model's maximum context window, leading to truncated data or degraded recall (the "lost in the middle" effect).
2. LLM Instruction Conflicts (Issue)
2. LLM Instruction Conflicts (Issue)
Pre-computed vs. Raw Transcript:
The prompt explicitly instructs the model:
"
Do not
invent, override, or recalculate scores"
but later says,
"For
what was actually said
, still rely on the
transcript
."
This creates a cognitive conflict for the LLM. If the raw transcript contradicts the pre-computed
justification
, the LLM might struggle with which source of truth to prioritize, potentially leading to hallucinations or contradictory summaries.
Prompt Complexity:
The more rules you add about
how
to read JSON formatting and
what
not to do, the less attention the model pays to the actual user query. This is a common bottleneck in prompt engineering known as instruction bloat.
3. Edge Cases in Formatting (Issue)
3. Edge Cases in Formatting (Issue)
Timestamp Limitations:
The instructions strictly define timestamps as
MM:SS
. This works fine for standard calls, but for longer meetings (over an hour), it either forces an awkward format (e.g.,
85:30
) or breaks if the system outputs
HH:MM:SS
.
Decimal vs. Whole Numbers:
The prompt specifies that the overall AI Score might be a decimal (average), but the individual rule score is a "Whole number
1–5
". If the upstream pipeline accidentally passes a decimal for a rule score, the LLM might get confused based on these rigid instructions.
How are you currently handling pagination or chunking for these calls—are you limiting the number of calls that can be passed into the full context at once to avoid token limits?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications
More
More
Sections
Sections
CS Day-to-day
🚀 Getting started Guide
🪬 Just CS Data
👉 Daily Operations
🗓️ Weekly prep
🤑 Renewals and Upsell
🚨 Risk and Churn Analytics
Implementation
Impl Projects
Trial Opps (Under Review)
Stoyan's clients
Content Explorer
Content Explorer
Tab icon For you
For you
Tab icon Sections
Sections
Tab icon Pages
Pages
Tab icon Archived
Archived
Add new
Add new
Search...
No content to display
The content explorer contains the Pages and Sections you have access to, and lets you customize your workspace
Add new
Add new
Content Explorer
Content Explorer
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Explore Keynote
Last edited
All Active Renewal Opps
2 minutes ago
All Existing Clients
15 minutes ago
My Renewals next 2Qs
17 minutes ago
OD Tasks
17 minutes ago
First 30 days to adoption
20 minutes ago
Explore community templates
Page templates
Section templates
Julia from Planhat
Julia
from Planhat
Close
Improved Task dependencies in Workflows
Improved Task dependencies in Workflows
Introducing highly requested features for task dependencies within Workflows. These allow project management to better correspond with real-world delivery:
Tasks can have multiple dependencies, across phases
Dependent task dates automatically update when a parent task is moved
Dependent tasks are assigned dates when a workflow is applied
Read more in our
docs opens in new tab
docs
.
...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22654
|
|
22655
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Show thinking
Gemini said
Gemini said
Here is a summary of the changes in the provided code diff:
AI Call Scoring Additions
AI Call Scoring Additions
Pre-computed Scores:
Added strict instructions to treat the
ai_call_score
as pre-computed data. The system must interpret and summarize the provided scores rather than inventing or recalculating them.
Context Breakdown:
*
Short Context:
Now displays the
AI Scorecard
name and the overall
AI Score
(the average of per-rule scores).
Full Context:
Details the
ai_call_score
object, breaking down individual rules. Each rule includes a title, prompt, a 1–5 score, a brief justification, and up to three timestamped speaker references (MM:SS).
Application Rules:
Instructs the system to use these scores for coaching summaries, trends, and comparisons, but dictates that it must still rely on the actual transcript for direct quotes.
Grammar and Formatting Cleanup
Grammar and Formatting Cleanup...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22655
|
|
22656
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Show thinking
Gemini said
Gemini said
Here is a summary of the changes in the provided code diff:
AI Call Scoring Additions
AI Call Scoring Additions
Pre-computed Scores:
Added strict instructions to treat the
ai_call_score
as pre-computed data. The system must interpret and summarize the provided scores rather than inventing or recalculating them.
Context Breakdown:
*
Short Context:
Now displays the
AI Scorecard
name and the overall
AI Score
(the average of per-rule scores).
Full Context:
Details the
ai_call_score
object, breaking down individual rules. Each rule includes a title, prompt, a 1–5 score, a brief justification, and up to three timestamped speaker references (MM:SS).
Application Rules:
Instructs the system to use these scores for coaching summaries, trends, and comparisons, but dictates that it must still rely on the actual transcript for direct quotes.
Grammar and Formatting Cleanup
Grammar and Formatting Cleanup
Typo Corrections:
Fixed minor grammatical errors, such as changing "contexts" to "context" and "utlizes" to "utilizes".
String Formatting:
Cleaned up the markdown link instructions by removing trailing newline and quotation artifacts (
\n"
) from the text strings.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said are there some issues and bottlenecks
You said
are there some issues and bottlenecks
Listen
Show thinking
Gemini said
Gemini said
Looking closely at the system instructions in the diff, there are definitely a few potential prompt engineering issues and bottlenecks introduced by these additions. When you ask a Large Language Model (LLM) to juggle large transcripts alongside complex JSON scoring objects, it creates specific friction points.
Here is a breakdown of the potential issues and bottlenecks based on the changes:
1. Token Consumption and Context Bloat (Bottleneck)
1. Token Consumption and Context Bloat (Bottleneck)
Massive Payload Size:
By injecting the full
ai_call_score
object into the context (which includes rule names, prompts, scores, text justifications, and up to three timestamps
per rule
), the token count per call will skyrocket.
Context Window Limits:
The prompt states:
"The full call context includes all calls data available..."
If a user filters for 5 or 10 calls, injecting the transcripts
plus
these extensive AI scoring arrays could easily hit the model's maximum context window, leading to truncated data or degraded recall (the "lost in the middle" effect).
2. LLM Instruction Conflicts (Issue)
2. LLM Instruction Conflicts (Issue)
Pre-computed vs. Raw Transcript:
The prompt explicitly instructs the model:
"
Do not
invent, override, or recalculate scores"
but later says,
"For
what was actually said
, still rely on the
transcript
."
This creates a cognitive conflict for the LLM. If the raw transcript contradicts the pre-computed
justification
, the LLM might struggle with which source of truth to prioritize, potentially leading to hallucinations or contradictory summaries.
Prompt Complexity:
The more rules you add about
how
to read JSON formatting and
what
not to do, the less attention the model pays to the actual user query. This is a common bottleneck in prompt engineering known as instruction bloat.
3. Edge Cases in Formatting (Issue)
3. Edge Cases in Formatting (Issue)
Timestamp Limitations:
The instructions strictly define timestamps as
MM:SS
. This works fine for standard calls, but for longer meetings (over an hour), it either forces an awkward format (e.g.,
85:30
) or breaks if the system outputs
HH:MM:SS
.
Decimal vs. Whole Numbers:
The prompt specifies that the overall AI Score might be a decimal (average), but the individual rule score is a "Whole number
1–5
". If the upstream pipeline accidentally passes a decimal for a rule score, the LLM might get confused based on these rigid instructions.
How are you currently handling pagination or chunking for these calls—are you limiting the number of calls that can be passed into the full context at once to avoid token limits?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications
More
More
Sections
Sections
CS Day-to-day
🚀 Getting started Guide
🪬 Just CS Data
👉 Daily Operations
🗓️ Weekly prep
🤑 Renewals and Upsell
🚨 Risk and Churn Analytics
Implementation
Impl Projects
Trial Opps (Under Review)
Stoyan's clients
Content Explorer
Content Explorer
Tab icon For you
For you
Tab icon Sections
Sections
Tab icon Pages
Pages
Tab icon Archived
Archived
Add new
Add new
Search...
No content to display
The content explorer contains the Pages and Sections you have access to, and lets you customize your workspace
Add new
Add new
Content Explorer
Content Explorer
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Explore Keynote
Last edited
All Active Renewal Opps
2 minutes ago
All Existing Clients
15 minutes ago
My Renewals next 2Qs
17 minutes ago
OD Tasks
17 minutes ago
First 30 days to adoption
20 minutes ago
Explore community templates
Page templates
Section templates
Julia from Planhat
Julia
from Planhat
Close
Improved Task dependencies in Workflows
Improved Task dependencies in Workflows
Introducing highly requested features for task dependencies within Workflows. These allow project management to better correspond with real-world delivery:
Tasks can have multiple dependencies, across phases
Dependent task dates automatically update when a parent task is moved
Dependent tasks are assigned dates when a workflow is applied
Read more in our
docs opens in new tab...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22656
|
|
22657
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Show thinking
Gemini said
Gemini said
Here is a summary of the changes in the provided code diff:
AI Call Scoring Additions
AI Call Scoring Additions
Pre-computed Scores:
Added strict instructions to treat the
ai_call_score
as pre-computed data. The system must interpret and summarize the provided scores rather than inventing or recalculating them.
Context Breakdown:
*...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22657
|
|
22658
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
You said I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected. Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
You said
I’m on page “<tabTitle>JY-20361: Add call scores in Panorama by steliyan-</tabTitle>” with “<selection>@@ -4,7 +4,7 @@ Today is {date_today}.445System instructions:5System instructions:6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.6- You must answer using markdown. Do not use html tags in your response even if requested by the user's question.7-- The contexts includes data for call shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.7+- The context includes data for calls shortlisted through user-applied filters. Note that the calls might not relate to the same deal or not even be by the same sales rep.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.8 - The full call context includes all calls data available while the short call context contains only an overview of the calls that are analysed. Refer to the short call context for quick reference and to see the overall picture.9- The calls are ordered in chronological order. 9- The calls are ordered in chronological order. 10- Here’s how to use the call context:10- Here’s how to use the call context:@@ -16,6 +16,15 @@ System instructions:16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.16 - Frame answers with awareness of the company’s ICP, deal cycle, and sales motion.17 - Evaluate statements or objections based on how the team operates and what success looks like.17 - Evaluate statements or objections based on how the team operates and what success looks like.18 - Position responses in light of known competitors and market dynamics.18 - Position responses in light of known competitors and market dynamics.19+ - AI call score (`ai_call_score` in the full call JSON): When present, treat it as **pre-computed** output from your team’s AI call-scoring pipeline (the same kind of scoring as the `/call/ai-call-scoring` endpoint). **Do not** invent, override, or recalculate scores; interpret and summarize what is given.20+ - **Short call context:** **AI Scorecard** is the name of the scorecard applied to that call; **AI Score** is the **overall** score for that scorecard (the average of its per-rule scores, possibly shown as a decimal).21+ - **Full call context:** The `ai_call_score` object may include `ai_scorecard_name`, `score` (overall for that scorecard), and `ai_scorecard_rules`. For each rule when listed:22+ - `rule_name`: Title of the criterion.23+ - `rule_prompt`: The criterion text that was evaluated.24+ - `score`: Whole number **1–5** measuring how well the call satisfied that criterion against `rule_prompt` (1 = no evidence / not discussed or contrary; 5 = strong, clear evidence on the call).25+ - `justification`: Short rationale grounded in what happened on the call.26+ - `justification_timestamps`: Up to three entries with speaker **name** and **timestamp** (MM:SS in the recording) highlighting where the justification is supported.27+ - Use scores for coaching summaries, trends across calls, or quick comparisons when relevant. For **what was actually said**, still rely on the **transcript** (you may cross-reference rule timestamps when helpful).19- Use the Message History to:28- Use the Message History to:20 - Maintain continuity if the current question refers to previous exchanges.29 - Maintain continuity if the current question refers to previous exchanges.21 - Clarify or resolve ambiguities if the question depends on prior messages.30 - Clarify or resolve ambiguities if the question depends on prior messages.@@ -28,10 +37,10 @@ System instructions:28 - All factual claims must be supported by one or more references to relevant calls.37 - All factual claims must be supported by one or more references to relevant calls.29 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.38 - Use Markdown link syntax ([link text](URL)) and place links inline within sentences. Do not use footnotes, reference sections, or bare URLs. Integrate the reference links directly within the relevant parts of your response, rather than in a separate section.30 - Use markdown links in the format [link text](/playback/{{call_id}})39 - Use markdown links in the format [link text](/playback/{{call_id}})31- - Use descriptive link that utlizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.\n"40+ - Use descriptive link text that utilizes the call name. Do not use call time stamps in the link text even if the link itself contains a time stamp, e.g. use 'Call Name' instead of 'Call Name at 10:00'. Never use call ids as link text.32- - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)\n"41+ - Good example of link text: [Call Name](/playback/1234567890?apFrom=123)33- - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)\n"42+ - Bad example of link text: [Call Name at 12:34](/playback/1234567890?apFrom=123) (do not use call time stamps in the link text)34- - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)\n\n"43+ - Bad example of links: [Call Name on November 12, 2025](/playback/1234567890?apFrom=123) (do not use dates in the link text)35 - You might back your statements with examples from the provided call transcripts in addition to the reference links.44 - You might back your statements with examples from the provided call transcripts in addition to the reference links.36- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.45- Be specific. Use names of accounts, clients and persons involved. Don't just say "one client" or "a client"! If no account is available, use the call title as a reference.37- If the question or context is unclear, request clarification or highlight ambiguities.46- If the question or context is unclear, request clarification or highlight ambiguities.</selection>” selected.
Please summarize the selection using precise and concise language. Use headers and bulleted lists in the summary, to make it scannable. Maintain the meaning and factual accuracy.
Expand
Listen
Show thinking
Gemini said
Gemini said
Here is a summary of the changes in the provided code diff:
AI Call Scoring Additions
AI Call Scoring Additions
Pre-computed Scores:
Added strict instructions to treat the
ai_call_score
as pre-computed data. The system must interpret and summarize the provided scores rather than inventing or recalculating them.
Context Breakdown:
*
Short Context:
Now displays the
AI Scorecard
name and the overall
AI Score
(the average of per-rule scores).
Full Context:
Details the
ai_call_score
object, breaking down individual rules. Each rule includes a title, prompt, a 1–5 score, a brief justification, and up to three timestamped speaker references (MM:SS).
Application Rules:
Instructs the system to use these scores for coaching summaries, trends, and comparisons, but dictates that it must still rely on the actual transcript for direct quotes.
Grammar and Formatting Cleanup
Grammar and Formatting Cleanup
Typo Corrections:
Fixed minor grammatical errors, such as changing "contexts" to "context" and "utlizes" to "utilizes".
String Formatting:
Cleaned up the markdown link instructions by removing trailing newline and quotation artifacts (
\n"
) from the text strings.
Good response
Bad response
Share & export
Copy
Show more options
Copy prompt
Edit
You said are there some issues and bottlenecks
You said
are there some issues and bottlenecks
Listen
Show thinking
Gemini said
Gemini said
Looking closely at the system instructions in the diff, there are definitely a few potential prompt engineering issues and bottlenecks introduced by these additions. When you ask a Large Language Model (LLM) to juggle large transcripts alongside complex JSON scoring objects, it creates specific friction points.
Here is a breakdown of the potential issues and bottlenecks based on the changes:
1. Token Consumption and Context Bloat (Bottleneck)
1. Token Consumption and Context Bloat (Bottleneck)
Massive Payload Size:
By injecting the full
ai_call_score
object into the context (which includes rule names, prompts, scores, text justifications, and up to three timestamps
per rule
), the token count per call will skyrocket.
Context Window Limits:
The prompt states:
"The full call context includes all calls data available..."
If a user filters for 5 or 10 calls, injecting the transcripts
plus
these extensive AI scoring arrays could easily hit the model's maximum context window, leading to truncated data or degraded recall (the "lost in the middle" effect).
2. LLM Instruction Conflicts (Issue)
2. LLM Instruction Conflicts (Issue)
Pre-computed vs. Raw Transcript:
The prompt explicitly instructs the model:
"
Do not
invent, override, or recalculate scores"
but later says,
"For
what was actually said
, still rely on the
transcript
."
This creates a cognitive conflict for the LLM. If the raw transcript contradicts the pre-computed
justification
, the LLM might struggle with which source of truth to prioritize, potentially leading to hallucinations or contradictory summaries.
Prompt Complexity:
The more rules you add about
how
to read JSON formatting and
what
not to do, the less attention the model pays to the actual user query. This is a common bottleneck in prompt engineering known as instruction bloat.
3. Edge Cases in Formatting (Issue)
3. Edge Cases in Formatting (Issue)
Timestamp Limitations:
The instructions strictly define timestamps as
MM:SS
. This works fine for standard calls, but for longer meetings (over an hour), it either forces an awkward format (e.g.,
85:30
) or breaks if the system outputs
HH:MM:SS
.
Decimal vs. Whole Numbers:
The prompt specifies that the overall AI Score might be a decimal (average), but the individual rule score is a "Whole number
1–5
". If the upstream pipeline accidentally passes a decimal for a rule score, the LLM might get confused based on these rigid instructions.
How are you currently handling pagination or chunking for these calls—are you limiting the number of calls that can be passed into the full context at once to avoid token limits?
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Pro
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22658
|
|
22746
|
Save password for planhat.com?
Username
[EMAIL]
Pa Save password for planhat.com?
Username
[EMAIL]
Password
[PASSWORD_DOTS]
Not now
More actions
Save
New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab...
|
Firefox
|
Home — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22746
|
|
22747
|
Save password for planhat.com?
Username
[EMAIL]
Pa Save password for planhat.com?
Username
[EMAIL]
Password
[PASSWORD_DOTS]
Not now
More actions
Save
New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles...
|
Firefox
|
Home — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22747
|
|
22748
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications
Notifications
No notifications to display
You are all caught up!
More
More
Sections
Sections
CS Day-to-day
🚀 Getting started Guide
🪬 Just CS Data
👉 Daily Operations
🗓️ Weekly prep
🤑 Renewals and Upsell
🚨 Risk and Churn Analytics
Implementation
Impl Projects
Trial Opps (Under Review)
Stoyan's clients
Content Explorer
Content Explorer
Tab icon For you
For you
Tab icon Sections
Sections
Tab icon Pages
Pages
Tab icon Archived
Archived
Add new
Add new
Search...
No content to display
The content explorer contains the Pages and Sections you have access to, and lets you customize your workspace
Add new
Add new
Content Explorer
Content Explorer
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Explore Keynote
Last edited
All Active Renewal Opps
5 minutes ago
All Existing Clients
18 minutes ago
My Renewals next 2Qs
20 minutes ago
OD Tasks
20 minutes ago
First 30 days to adoption
23 minutes ago
Explore community templates
Page templates
Section templates...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22748
|
|
22749
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22749
|
|
22750
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22750
|
|
22751
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals....
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22751
|
|
22752
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications
More
More
Sections
Sections
CS Day-to-day
🚀 Getting started Guide
🪬 Just CS Data
👉 Daily Operations
🗓️ Weekly prep
🤑 Renewals and Upsell
🚨 Risk and Churn Analytics
Implementation
Impl Projects
Trial Opps (Under Review)
Stoyan's clients
Content Explorer
Content Explorer
Tab icon For you
For you
Tab icon Sections
Sections
Tab icon Pages
Pages
Tab icon Archived
Archived
Add new
Add new
Search...
No content to display
The content explorer contains the Pages and Sections you have access to, and lets you customize your workspace
Add new
Add new
Content Explorer
Content Explorer
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Explore Keynote
Last edited
All Active Renewal Opps
5 minutes ago
All Existing Clients
18 minutes ago
My Renewals next 2Qs
20 minutes ago
OD Tasks
20 minutes ago
First 30 days to adoption
23 minutes ago
Explore community templates
Page templates
Section templates...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22752
|
|
22753
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22753
|
|
22754
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22754
|
|
22755
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22755
|
|
22756
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22756
|
|
22759
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications
More
More
Sections
Sections
CS Day-to-day
🚀 Getting started Guide
🪬 Just CS Data
👉 Daily Operations
🗓️ Weekly prep
🤑 Renewals and Upsell
🚨 Risk and Churn Analytics
Implementation
Impl Projects
Trial Opps (Under Review)
Stoyan's clients
Content Explorer
Content Explorer
Tab icon For you
For you
Tab icon Sections
Sections
Tab icon Pages
Pages
Tab icon Archived
Archived
Add new
Add new
Search...
No content to display
The content explorer contains the Pages and Sections you have access to, and lets you customize your workspace
Add new
Add new
Content Explorer
Content Explorer
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries
Organizing content: Pages, Sections and Libraries...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22759
|
|
22775
|
QuickTime PlayerPetko KashinskiScreen shareChromeF QuickTime PlayerPetko KashinskiScreen shareChromeFileFileEditViewWindowHelpEditViewHistoryBookmarksProfilesTabWindowHelp(NGreetiScorecandre;f wilsonws.planhat.com/jiminny/apps?id=66ceb97643c2530bb32c8bb6АIKB• ChatPlayground Al....Jiminny - Calenda...M GMail• My Calendly - Eve...+ BackSearch Jiminny83 App Center& UP > PH UXE Al apps& Created by meG Recentty most activeIntegrations8 AutomationsP Private apps8 EditorEa Runs® DataCall Ar= PH New UI Login*= Al Notes: O11Petko ...Screen...&(ablj Support Daily - in 4h 40 m100% (8•Tue 12 May 10:20:51JiminnM InboxGet Starting with J...= Nate R( Apps= AрChloe Onboarding…BuildirQu Userp+ CX Journey SMB....+8• Mon 11 May 12:17New te+f Work40 +.Petko•• XIEnabled• Huddle with Lukas KovalikLeave...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22775
|
|
22776
|
rireroxFavouritesjiminny• Recents* Applications|9 rireroxFavouritesjiminny• Recents* Applications|9 Documentsii lukasIcloud• iCloud Drive992 Svnc toldeLocations0 DXP4800PLUS-B5F A49 Network• CRM• Orange• Red• Yellow• Purple|• All lagsProtllesworkv 2026• Daily 2026-05-12.mp4_ PLanhat Petko interest event 2026-05-11.mp4• Dailv 2026-05-11.mo4wu Daily 2026-05-08.mp4Iя 1-1 2026-05-07.mp4& Dailv 2026-05-07mo4us 1-1 2026-04-24.mp4= Daily 2026-04-24.mp4User Pilot introduction Adi 2026-04-23.mp4nDaily 2026-04-22 mnлwn Refinement 2026-04-06.mp4• Dailv 2026-04-21.mo4D Refinement 2026-04-20.mp4Dally 4020-04-20.Mp4L Daily 2026-04-17.mo4ru Daily 2026-04-16.mp4. Retro 2026-04-14.mp4n Daily 2026-04-14.mn/• User pilot (Adi) 2026-04-09.mp4• Daily 2026-04-09.mp4Daily 2026-04-07.mp4Daily 2026-04-06.mp4=Daily 2026-04-03.mp4lax Planning 2026-04-01 & task split.mp4l: Retro 2026-03-31.mp4Daily 2026-03-31.mp4•: Refinement 2026-03-30.m04m Daily 2026-03-30.mp4= Dallv 2026-03-26.m04B Daily 2026-02-24 mn4ment 2026-03-23.mo4-• Daily 2026-03-23.mp4• BE chaoter 2026-03-20.mo4• Daily 2026-03-20.mp4am Planing 2026-03-18-converted.mp4= Retinement 2026-02-09-converted.mo4)eR Daily 2026-02-10 mn/- Review 2026-03-18.mp4am Planing 2026-03-18.mp4F Retro 2026-03-17 mn4- Daily 2026-03-17.mp4Refinement 2026-03-16.mp4• Dailv 2026-03-16.mo4F Daily 2026.02-12 mn/ra 1-1 2026-03-12.mpDailv 2026-03-12.mp4aa Daily 2026-03-11.mn/Dailv 2026-03-10.mp4xI Refinement 2026-03-09.mp4e Dailv 2026-03-09.mo4tanailu bane na.ne mnllJiminny¿ Profile-AllItems• FavoritesWatchtower< Developen() Emolovee( EngineeringIntearation Account• JiminnvTAGSO 2FA|• CSV Import 28.01.2.• LastPacc Imnort 1.11dawterv!New TabJy 20820 es reindex stream mode4 [JY-20725] [HubSpot] Optimise Cl@ JY-20725 add HS rate limit handlilPipelines - jiminny/app• Pull requests • jiminny/app(JY-20773] User Pilot not receivinJY-20773 fix user pilot tracking ofiNY-20776 Automated report - seTypeError: League|Flysystem\FilesA TypeError: League\Flysystem\FilesPlatform Sprint 3 02 - Platform Te• JY-20625 | JY-20742 | MCP POC kG LLM pricing overview with the mo:A Planhal& Content Explorer• Loain- New Tab• • ws.planhat.com/jiminny/home/content-expldsupoont Dally • In 41 40M— Add new vGoogle Gemintdifferent versions and regions, vou can trynavigating directly. However, note thatws.planhat.com is a global entry point for theupgraded plattorm• Try navigating to: https://ws.planhat.com• If your account has been migrated to theupgraded version, it should recognize yourseccion or nromnt vou to lod in• Note: If your data is specifically hosted onthe eu3 cluster, the system mayautomatically redirect you to a regionalversion of the upgraded Ul (e.g., ws-eu3.planhat.com )2. The In-App "Switch" (If Available)If your tenant is eligible for the upgrade but youare still in the classic "app" view, look for theseUelements:• The Top Gray Bar: Click on vour TenantName/Logo in the top-left corner. ThisAfton anenc the "Clnhal Toalc" manin• Upgrade Prompts: In some instances,Planhat places a "Try the new Planhat" or"Upgraded Planhat" toggle in the Helpmenu (the "?" icon in the top right) or as abanner at the too of the screen.Why use ws.planhat.com?You likely need this URL to access newer "GlobalO Enter a prompt for GeminiFastvYour Jiminny chats aren't used to improve our models. Gemini tAlcan mike micnkec co dolidle chockt Yolr orivaev domiinSummarize pageJiminny• Content Explorer• Data ExplorerCalendar• Notifications*** MoreCS Dav-to-davJ Getting started Guide—ust es Data Dailv OverationsWeekly prep•Renewals and Upsell€ Risk and Churn An..ImolementationImnl DroiocteTrial Opps (Under Rev...Stovan's clientsSearch JiminnyFor youn SectionsPadesaArchivedi© Content Explorer• Search.No content to displayThe content explorer contains the Pages and Sections younave access to, ana lers vou customize vour workspace+ Add new›M Content ExploreM Oraanizina content: Pages. Sections and LibrariesM Oraanizina content: Paaes. Sections and Libraries100% 5• lue 1z May 10.20:0'L LukasKe discover yourWorkspaceExplore KeynoteLast editedE All Active Renewal OppsEB All Existing Clients# My Renewals next 20s# OD Tasks8 First 30 days to adoptionExolore communitv temolatesPage templates( Section templates5 minutes ago21 minutes agd21 minutes ago24 minutes add...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22776
|
|
22777
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22777
|
|
22778
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications
More
More
Sections
Sections
CS Day-to-day
🚀 Getting started Guide
🪬 Just CS Data
👉 Daily Operations
🗓️ Weekly prep
🤑 Renewals and Upsell
🚨 Risk and Churn Analytics
Implementation
Impl Projects
Trial Opps (Under Review)
Stoyan's clients
Content Explorer
Content Explorer
Tab icon For you
For you
Tab icon Sections
Sections
Tab icon Pages
Pages
Tab icon Archived
Archived
Add new
Add new
Search...
No content to display
The content explorer contains the Pages and Sections you have access to, and lets you customize your workspace
Add new
Add new
Content Explorer
Content Explorer
Organizing content: Pages, Sections and Libraries...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22778
|
|
22779
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22779
|
|
22780
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)
If your tenant is eligible for the upgrade but you are still in the classic "app" view, look for these UI elements:
The Top Gray Bar:
Click on your
Tenant Name/Logo
in the top-left corner. This often opens the "Global Tools" menu.
Upgrade Prompts:
In some instances, Planhat places a "Try the new Planhat" or "Upgraded Planhat" toggle in the Help menu (the
"?" icon
in the top right) or as a banner at the top of the screen.
Why use ws.planhat.com?
Why use ws.planhat.com?
You likely need this URL to access newer "Global Tools" and features that are only available in the upgraded version, such as:
Data Model Manager:
For advanced field and object configuration.
Portal Manager:
To manage customer-facing portals.
Workflows:
The newer engine for automating projects and sequences.
Federated Search:
Located in the middle of the top gray bar in the
ws
version.
Important Troubleshooting:
Permissions:
If you try to access
ws.planhat.com
and get an error or a blank screen, your user
Role
may lack the "Admin Access" or "Upgraded Access" permissions. You will need a current Admin to enable these for you in the
Settings > Users & Roles
section of the current app.
NPS Campaigns:
Note that as of recent updates, some features like NPS configuration might still require you to briefly switch back to the classic
app.planhat.com
view while they are being finalized for the
ws
environment.
Good response
Bad response
Redo
Share & export
Copy
Show more options
Enter a prompt for Gemini
encrypted
Enter a prompt for Gemini
encrypted
Open upload file menu
Tools
Open mode picker
Fast
Microphone
Send message
Your Jiminny chats aren’t used to improve our models. Gemini is AI. It can make mistakes, so double check it.
Your privacy & Gemini Opens in a new window
Your privacy & Gemini
Opens in a new window
Summarize page
Summarize page
J J Jiminny
J
Jiminny
Search Jiminny ⌘K
Search Jiminny
⌘
K
L
Lukas
Content Explorer
Content Explorer
Data Explorer
Data Explorer
Calendar
Calendar
Notifications
Notifications
More
More
Sections
Sections
CS Day-to-day
🚀 Getting started Guide
🪬 Just CS Data
👉 Daily Operations
🗓️ Weekly prep
🤑 Renewals and Upsell
🚨 Risk and Churn Analytics
Implementation
Impl Projects
Trial Opps (Under Review)
Stoyan's clients
Content Explorer
Content Explorer
Tab icon For you
For you
Tab icon Sections
Sections
Tab icon Pages
Pages
Tab icon Archived
Archived
Add new
Add new
Search...
No content to display
The content explorer contains the Pages and Sections you have access to, and lets you customize your workspace...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22780
|
|
22781
|
New Tab
New Tab
Jy 20820 es reindex stream model h New Tab
New Tab
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
Jy 20820 es reindex stream model hydration by Vasil-Jiminny · Pull Request #12059 · jiminny/app
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
[JY-20725] [HubSpot] Optimise CRM rematching on delete hubspot accounts/contacts - Jira
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
JY-20725 add HS rate limit handling on activities rematching by LakyLak · Pull Request #12066 · jiminny/app
Pipelines - jiminny/app
Pipelines - jiminny/app
Pull requests · jiminny/app
Pull requests · jiminny/app
[JY-20773] User Pilot not receiving events on report generated - Jira
[JY-20773] User Pilot not receiving events on report generated - Jira
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
JY-20773 fix user pilot tracking ofr automated report generated by LakyLak · Pull Request #12024 · jiminny/app
[JY-20776] Automated report - sentry - Jira
[JY-20776] Automated report - sentry - Jira
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
TypeError: League\Flysystem\Filesystem::has(): Argument #1 ($location) must be of type string, null given, called in /home/jiminny/vendor/laravel/framework/src/Illuminate/Filesystem/FilesystemAdapter.php on line 218 — jiminny — app
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
Platform Sprint 3 Q2 - Platform Team - Scrum Board - Jira
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
JY-20625 | JY-20742 | MCP POC by yalokin-jiminny · Pull Request #12036 · jiminny/app
LLM pricing overview with the most actual prices - Google Search
LLM pricing overview with the most actual prices - Google Search
Planhat
Planhat
Content Explorer
Content Explorer
Close tab
Login
Login
New Tab
Customize sidebar
Close Google Gemini (⌃X)
Tabs from other devices
Open history (⇧⌘H)
Open bookmarks (⌘B)
AI Chat settings
Close
WORK, Google Account: [EMAIL]
Main menu
New Chat
Open menu for conversation actions.
Conversation with Gemini
Conversation with Gemini
Copy prompt
Edit
You said I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
You said
I am on https://app-eu3.planhat.com/ how to get to ws.planhat.com
Listen
Gemini said
Gemini said
To get to
ws.planhat.com
(which is the address for the "Upgraded Planhat" or "Next Generation" interface) while you are currently on the EU regional server (
app-eu3.planhat.com
), you have two primary options:
1. The Manual URL Change
1. The Manual URL Change
Because Planhat uses specific subdomains for different versions and regions, you can try navigating directly. However, note that
ws.planhat.com
is a global entry point for the upgraded platform.
Try navigating to:
https://ws.planhat.com
https://ws.planhat.com
If your account has been migrated to the upgraded version, it should recognize your session or prompt you to log in.
Note:
If your data is specifically hosted on the
eu3
cluster, the system may automatically redirect you to a regional version of the upgraded UI (e.g.,
ws-eu3.planhat.com
).
2. The In-App "Switch" (If Available)
2. The In-App "Switch" (If Available)...
|
Firefox
|
Content Explorer — Work
|
ws.planhat.com/jiminny/home/content-explorer
|
22781
|