Peter Jodeleit
- Total activity 15
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 1
- Subscriptions 5
Activity overview
Latest activity by Peter Jodeleit-
Peter Jodeleit commented,
Das liest sich so, als würden die Daten nur in der Vorschau benötigt.Statt die Daten redundant zu speichern könnte man sie dann auch per API in der Vorschau-Version des Frontends dynamisch aus Firs...
-
Peter Jodeleit commented,
Ein Hinweis von mir: Die Idee hinter dem von Holger beschriebenem Vorgehen ist, das "globale Inhalte" ja auf der Webseite / in der PWA normalerweise auch angezeigt werden (z.B. im Footer). Und dort...
-
Peter Jodeleit commented,
Thank you for your question. First, please note that we do not actually apply any limitation, see my comment above yours. Then, to your question: There is no "that best practice", this heavily depe...
-
Peter Jodeleit commented,
We would like to clarify the information in this post. With our previous communication, we wanted to be transparent that these jobs are highly resource-intensive operations intended for exceptiona...
-
Peter Jodeleit commented,
Official comment Since some questions already popped up: If you or your colleagues didn't get a dedicated request for communication earlier this does mean your usage pattern is safe and you will not be affected by ...
-
Peter Jodeleit created a post,
[Update] Introducing a rate limit for CaaS synchronization jobs
Answered[This information is partly outdated, for an update see the comment below]We are introducing a rate limit for the CaaS synchronization jobs to protect system performance and ensure a c...
-
Peter Jodeleit commented,
Update: Clarified customer impact.
-
Peter Jodeleit created a post,
[Incident] CaaS Connect v3.85.0 – Unintended behavior change for remote datasets
Hi everyone, We want to inform you about an issue introduced with CaaS Connect version 3.85.0, which was rolled out to FirstSpirit SaaS instances this Wednesday (February 18th, to DEV and QA last w...
-
Peter Jodeleit commented,
Wie Holger schreibt, ist nicht jeder Agent in jedem Kontext verfügbar. Wenn du deinen Use-Case ohne den GID Agent nicht lösen kannst, dann lege doch bitte ein Support-Ticket dafür an und schildere ...