Home General Discussion

Cloud Connector methods PUT and PATCH not working in version 11.8.2

Simon_ZeinhoferSimon_Zeinhofer Customer Advanced IT Monkey ✭✭✭
edited June 2023 in General Discussion

We updated to 11.8.2 this Saturday, and from this day on the PUT and PATCH Methods in the cloud connector are not working anymore.

We are able to get and create new work items via GET/POST, but every update fails with a timeout.

We also receive the following error message inside the webconsole logfile:

An error occurred during Pre-Save
System.NullReferenceException: Object reference not set to an instance of an object.
   at Cireson.ServiceManager.Services.Implementations.ProjectionPersistenceService.<SendActionLogWebhook>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cireson.ServiceManager.Services.Implementations.ProjectionPersistenceService.<CommitAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CallSite.Target(Closure , CallSite , Object )
   at CiresonWebConsole.Controllers.api.V3.ProjectionController.<Commit>d__6.MoveNext() in D:\a\1\s\Cireson.WebConsole\Cireson.ServiceManager.WebConsole\Controllers\api\V3\ProjectionController.cs:line 48
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CiresonWebConsole.Controllers.WebConsoleBaseController.<PreSave>d__57.MoveNext() in D:\a\1\s\Cireson.WebConsole\Cireson.ServiceManager.WebConsole\Controllers\WebConsoleBaseController.cs:line 320

This occured when I wanted to update the classification of an existing incident.

I already opened an Incident for that but maybe someone here might be able to help :)

Answers

This discussion has been closed.